The new parser has several advantages:
Usually when 4.0 template parsing produces an error, it is because you have included a WebObjects dynamic form element inside of a static HTML FORM element. Change the FORM element to a WOForm, and your component should operate normally again. An error may also arise if your HTML pages contain BODY or IMG tags with src parameters containing relative pathnames (absolute pathnames aren't a problem). Change the affected tags to WOBody and WOImage, respectively.
If you want, you can go back to the previous parser by implementing this method in your application class (shown in Java and WebScript):
public boolean requiresWOF35TemplateParser() { return true; } - requiresWOF35TemplateParser { return YES; }If you use the WebObjects 4.0 template parser, you might want to suppress the inclusion of HTML comments. Use the following methods, which have been added to WOApplication (as an alternative, you can use the option described in the section Command-Line Options):
WOApplication Template Parsing Methods.
Table of Contents Next Section