[Bug 57773] performance problems when using scopeless optional attributes

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=57773

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
I don't think there is anything we can do about this.

Supporting EL 3.0 means JSP 3.0 has to check the identifier to see if it is an
imported class or field. Class lookups are slow - largely due to the
ClassNotFoundException that is triggered when it fails.

We can avoid the CNFE by looking up the InputStream for the class rather than
trying to load the class. On the plus side this makes lookups when the
identifier is not a class ~4 times faster. The downside is it makes valid
lookups ~25% slower. I don't think this is a viable option.

I've added some information to the Tomcat 8 migration guide to explain this
issue and to recommend the work-around you are already applying.

We could add a Tomcat specific option to skip the class/field lookup in the
ScopedAttributeELResolver. I'm not a fan of this because:
- it would be Tomcat specific
- it would have to be a system property since this is a spec class
- it could not be applied per application - it would impact all applications
running on that instance

It this turns out to affect large numbers of users then the Tomcat specific
option is probably the answer but for now this is WONTFIX.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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