> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] > > Interesting approach. What worries me is how deeply it touches things, > from ICA to Template to nodes. > > Why couldn't this be implemented as a filter on the writer?
With a filter on the writer it would be impossible to turn off escaping on a reference-by-reference basis. Anyone who wants to insert strings of XML in a document will need this feature... I suspect the Turbine people will want this for the same reason I do - in order to do Screen/Layout processing (or in Maverick, a document aka wrapping transform), the output of the "inner" page is passed to the "outer" layout page as a String in the context. That string will of course contain html which must not be escaped. By adding a $foo:noescape syntax, it would only be necessary to add the property to the node and some code to check it in ASTReference. I think this is wonderful :-) My question: Why track the state of text outside of references? With a $foo:noescape option, the person writing the template can easily control the appropriate behavior inside of CDATA sections and the like. As a reference point, neither Struts nor JSTL have (or seem to require) this additional intelligence. Jeff Schnitzer [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
