| I just ran into an interesting feature/bug of the WO parser.
The following generates an error when NoSuchString is not in the wod:
<!-- <webobject name = "NoSuchString" -->
this doesn't
<!-- > <webobject name = "NoSuchString" -->
(There can be anything you like at the beginning of the comment, the import bit is that there is a '>' before the first WO tag)
If you make NoSuchString not error, the content is removed from the output unless you call setIncludeCommentsInResponses(true), in which case the first example is replaced with dynamic content but the second version is not. In order for commented wotags to be replaced with dynamic content the first '>' within the comment must belong to a WO tag, in which case all wotags within the comment will be parsed and rendered.
Is this a feature or a bug? If this is a feature, isn't that what WOHTMLCommentString is for? Should it be fixed? If so, what is the expected behaviour? Should WOLips validate components using this same logic, continue to validate all wotags commented or not, or not validate wotags in comments at all?
-- Seeya...Q
Quinton Dolan - email@hidden Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
|