Inline JSP2:
${fn:escapeXml(blah)}
That does however and in the cases you'd be worried about xml-escapage
isn't all that irritating. It does mean you have to worry though.
--jason
Jeff Schnitzer wrote:
This was a typo... the xml is not malformed. In JSTL you do:
<c:out value="${blah}"/>
This xml-escapes the output. You can also do ${blah} inline, but it
doesn't xml-escape the output (which is really irritating, imnsho).
Jeff
Robert Koberg wrote:
This whole idea of using <vel:sometag malformed-xml/> seems backward.
Serge Knystautas wrote:
On 8/22/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
(And I thought I was being so clever about the Context idea).
Another issue is that the emerging VSTL is useful for if's and set's
but shares JSTL's wordiness for straight output
(e.g. <c:out "${model.property}"/> instead of just $model.property).
JSTL lets you do just ${model.property} without the c:out. The
advantage to still using c:out at times is that it does XML escaping.
* modify Velocity core to support evaluation of expressions
* create new VSTL tag library in part that parallels JSTL
* add in macro capability (?)
* merge in veltag (?)
* document, create examples, website, etc.
One of the strengths of the current JSP specs are .tag files, which is
a cold fusion idea. I think it would be nice to use a similar
convention for macros. No idea how that fits though.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
