« Return to Thread: OGNL and JSP 2.1 - are there plans to fix?

Re: OGNL and JSP 2.1 - are there plans to fix?

by mraible :: Rate this Message:

Reply to Author | View in Thread

Here's what I've found out:

On Tomcat 6, the following will work to disable processing of #{}:

1. On a per-page basis using a page directive:

<%@ page deferredSyntaxAllowedAsLiteral="true" %>

2. Disable for all JSPs in web.xml:

    <jsp-config>
      <jsp-property-group>
        <url-pattern>*.jsp</url-pattern>
        <deferred-syntax-allowed-as-literal>true</deferred-syntax-allowed-as-literal>
      </jsp-property-group>
    </jsp-config>

For #2 to be valid, you have to use a Servlet 2.5 XSD.

AFAICT, this does *not* work in Jetty 6.1.x. However, I think this is a bug:

http://tinyurl.com/yr29fg

Matt
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

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

 « Return to Thread: OGNL and JSP 2.1 - are there plans to fix?