struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Musachy Barroso <>
Subject Re: ognl 2.7.3 performance
Date Tue, 03 Nov 2009 17:22:52 GMT
Well yes, that's by default, but with the new EL api you can plugin a
new EL resolver like:

 JspApplicationContext jspApplicationContext =
 jspApplicationContext.addELResolver(new CompoundRootELResolver());

and the container will delegate to that resolver. BTW the JUEL plugin
is in better shape than I thought, Tom are you out there?


On Tue, Nov 3, 2009 at 8:55 AM, Antonio Petrelli
<> wrote:
> 2009/11/3 Antonio Petrelli <>:
>> 2009/11/3 Musachy Barroso <>:
>>> We also have FreeMarker , Velocity and we have a lot of expression
>>> evaluations from Struts code itself.
>> And in this case you're right, EL at Struts-side is obligatory.
>> But exactly, is a bad idea to use the capability of the container to
>> resolve EL expressions into values?
>> This is just an idea.
> Another thing, sorry for the noise :-D
> If EL Expressions are interpreted Struts-side, this means that in JSP
> tags the attributes that represent expressions should not be "rtexpr"
> activated.
> This means that they might not have an expression, so you cannot write:
> <struts:tag expression="${myexpr}" />
> because it is not interpreted as a string, but as an expression
> illegally placed.
> So you should do funny things, like string composition, to let it work.
> Antonio
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message