It wouldn't even be a configuration change. Just drop the plugin jar in
your s2 project and you're using my value stack. (Most likely breaking
a lot of your OGNL) At this point, we execute the unified EL outside of
the JSP engine, within the tags/value stack. So at a minimum, if we
wanted to support EL at a JSP level, we'd have to create a new tld
file. I'm not sure how that would work with the existing tags, it's
been a while since I've written a taglib outside of s2/webwork. It all
depends on how seamlessly you would want it to work with existing JSP
taglibs, like JSTL. The work I've done would certainly be a darn good
start. If we needed a whole new taglib, I think that would be a good
amount of work.
Tom
Adam Hardy wrote:
Very interesting.
The situation at the moment is that EL and OGNL should not be used
together, for security reasons as I understand it, and therefore S2
doesn't allow EL. It seems the ideal solution is to offer the option
of either EL or OGNL, with only a change in one configuration option
needed to specify which.
Tom Schneider on 02/12/07 19:34, wrote:
I was working on a proof of concept for Unified EL:
http://cwiki.apache.org/S2PLUGINS/unified-el-plugin.html
I had a basic value stack up and running, however, I never took it
any farther than that. Richard Burton is planning on implemented an
MVEL stack in the near future, but he's waiting on some changes from
Chris Brock in MVEL itself.
I think in the long run, we really need a new tag library to fully
take advantage of the unfied EL. Even if we do that though, standard
unified EL is not as powerful as OGNL. We would need to extend the
language or be limited when compared to what is possible with OGNL
today. Maybe for some people that's not an issue, but I fear that
would keep some people from switching.
Tom
---------------------------------------------------------------------
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]
