There must be a way (or we should build a way) that Struts could
allow customization of the el that gets substituted before passing it
off to OGNL.
I would ask on the dev list and possibly even file a JIRA ticket on
this.
Thanks
--
James Mitchell
The Ruby Roundup
Hello,
I get the following error when trying to create a list with ognl:
org.apache.jasper.JasperException: /jspx/users/completeProfile.jspx(27,48)
#{'F':'Female','M':'Male'}
contains invalid expression(s): javax.el.ELException: Error Parsing:
#{'F':'Female','M':'Male'}
the code in jspx:
Found the answer in the opensymphony forum:
http://forums.opensymphony.com/thread.jspa?messageID=100059
On glassfish, it seems you have to disable EL:
!-- = Disable the JSP-EL, it messes up on pages with OGNL
=== --
jsp-config
jsp-property-group
--- Piero Sartini [EMAIL PROTECTED] wrote:
On glassfish, it seems you have to disable EL:
!-- = Disable the JSP-EL, it messes up on
pages with OGNL
=== --
jsp-config
jsp-property-group
url-pattern*.jspx/url-pattern
el-ignoredtrue/el-ignored
Will this issue get resolved in the future?
That may have to do with the JSF EL, which also uses #
as its escape char.
If that's the case, probably not?
That is the case. But why not? Its not JSF EL but JSP EL.
I don't think its good to be incompatible with JSP..
Sorry, meant to include this link:
http://today.java.net/pub/a/today/2006/03/07/unified-jsp-jsf-expression-language.html
d.
--- Dave Newton [EMAIL PROTECTED] wrote:
--- Piero Sartini [EMAIL PROTECTED] wrote:
On glassfish, it seems you have to disable EL:
!-- = Disable the
--- Piero Sartini [EMAIL PROTECTED] wrote:
I don't think its good to be incompatible with JSP..
It wasn't incompatible until 2.1, IIRC, and it was
JSF-only up until then, before the unification effort.
Maybe take it up w/ the OGNL folks? I agree that this
may cause a problem in some
7 matches
Mail list logo
