https://issues.apache.org/bugzilla/show_bug.cgi?id=57583
Bug ID: 57583
Summary: Performance issue evaluating EL in custom tags (tagx)
due to inefficient calls to java.lang.Class.forName()
Product: Tomcat 8
Version: 8.0.18
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Jasper
Assignee: dev@tomcat.apache.org
Reporter: jevge...@gmail.com
Method getValue of ScopedAttributeELResolver in some cases calls
ImportHandler.resolveClass(..) that ends up looking the class by name.
It seems that the look-up is made whenever a custom tag attribute that is not
initialized yet (==null) is used in EL. I have plenty of these cases in custom
tags, they are optional tag parameters, and this makes JSP rendering really
slow.
At the moment I've replaced lib/jsp-api.jar with Glassfish implementation and
it seems to do the trick. I hope the rendering result itself is not affected by
this substitution (I would be very thankful if someone could tell me what the
possible drawbacks might be, or provide arguments on why it is not a good idea
to replace jsp-api implementation).
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
