I don't know about the escaping, but #(msg.foo} is a shortcut for
outputText is only true functionally, and then only in the generic
sense that both will put text on the page. Ie, #{msg.foo} will
evaluate to a literal piece of text, but it is not the same thing as
using an outputText component.
thanks, but I posted 2 strings, one was escaped while the other was not.
Shouldn't it at least consistently escape or not escape?
On Wed, Oct 19, 2011 at 4:11 PM, Kito Mann kito.m...@virtua.com wrote:
Ted,
The strings will only be escaped if the component you're using escapes the
text. If
oh and in addition to the inconsistency between the 2 example strings, I
just checked, to the best of my knowledge #{msg.foo} is a short cut for
outputText tag,
The outputText tag, according to the jsf javadocs, says it is true by
default.
So, if that's true, shouldn't be escaped to quot; by
Ted,
The strings will only be escaped if the component you're using escapes the
text. If you're just embedding the expression in the page, it's not going to
be escaped, but you can use h:outputText -- this allows you to control
whether or not you want the text escaped.
---
Kito D. Mann | twitter:
4 matches
Mail list logo
