struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mraible <m...@raibledesigns.com>
Subject Re: OGNL and JSP 2.1 - are there plans to fix?
Date Thu, 02 Aug 2007 17:05:34 GMT



DNewfield wrote:
> 
> Dale Newfield wrote:
>> I've not tried...
> 
> And that's the problem right there.  Even just more web research found 
> an answer:
> 
> http://www.devzuz.org/blogs/bporter/2006/08/05/1154706744655.html
> 
> clearly answers my question: "But, to escape it with \#{ doesn't work on 
> Tomcat 5 and other 2.0 containers."
> 
> (And I wasn't subscribed to the struts-dev list long enough ago to 
> notice Musachy's similar workaround suggestion: 
> http://www.nabble.com/2.1-and-tooltips-tf3535099.html#a9867353 )
> 
> -Dale
> 

It also doesn't work on Jetty 6.1.x, but I think that's a bug in Jetty.

On another note (to quote the article above):



> With version 2.1 or later, the character sequence #{ represents a deferred
> expression, assuming the attribute has been declared to support deferred
> expressions in the TLD. If the attribute does not support deferred
> expressions, then the presence of the #{ character sequence results in a
> translation error.
> 

This seems to imply that if Struts produced a JSP 2.1 TLD for its tags, it
could turn off the support of #{} on a per-attribute basis.

Matt

-- 
View this message in context: http://www.nabble.com/OGNL-and-JSP-2.1---are-there-plans-to-fix--tf4103710.html#a11968579
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message