tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: EL system properties...possible to override per context?
Date Tue, 05 Jul 2011 13:21:43 GMT
On 05/07/2011 13:54, Dan Checkoway wrote:
> Thanks for the reply, Mark.  I realize tomcat is just conforming to the spec
> (rightly so), but I happen to disagree with the spec (jsp/el, not tomcat) in
> this one area.  Empty form fields being treated as "set to 0" is what I
> consider buggy...since we're throwing the term "buggy" around.  :-)
> 
> "Run two Tomcat instances" is something I could do, but you have to admit
> it's a brute force solution to a simple problem.
> 
> I see the same sort of suggestion got shot down about a year ago:
> 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48813
> 
> I understand wanting (insisting, for that matter) to isolate the EL parser
> from the servlet API.  Seems to me it would be nice if there was a choice
> between:
> - one EL parser is instantiated per engine (default behavior, parser shared
> among all contexts)
> - one EL parser is instantiated per context (and can be configured
> separately)
> 
> The EL parser itself wouldn't have to know anything about the servlet
> engine.  I believe the change would simply involve, for the most part,
> eliminating static variables (such as the one in question,
> AstValue.COERCE_TO_ZERO).  Moving those statics to an ELParserConfiguration
> type object might be the ticket?
> 
> Is that a reasonable request?

The request is reasonable. Bug 48813 didn't get closed because it was
unreasonable, the OP closed it as they found an alternative solution.

> What if I'm willing to help code it?  :-)

Since Tomcat is specification compliant, this would be an enhancement
and enhancement requests with patches always stand a better chance than
those without.

Keep in mind the following constraints:
- You can't change the javax.el API
- javax.el can't have any external dependencies
- Jasper can't depend directly on org.apache.el
- org.apache.el must not have any external dependencies

That list isn't exhaustive, but it gives you the general idea.

Mark



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message