https://issues.apache.org/bugzilla/show_bug.cgi?id=57141
Bug ID: 57141
Summary: JSP 2.3 & EL 3.0 Spec conflict w/Static Fields,
Methods, etc.
Product: Tomcat 8
Version: trunk
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: EL
Assignee: dev@tomcat.apache.org
Reporter: artfied...@gmail.com
EL 3.0 supports resolving static fields, methods etc. However I could not find
a mention of this in the JSP 2.3 spec when using the EL Resolvers. Since
ScopedAttributeELResolver is suppose to always set
context.propertyResolved(true); even if the attribute is not found, the el
processor never reaches the code to check for resolving a class. Making
${Boolean.TRUE} impossible to resolve from a JSP page.
>From my understanding even though JSP 2.3 does not mention supporting this
functionality, I believe it maybe intended. The proof I have of this starts
from following this stackoverflow article
http://stackoverflow.com/questions/24768377/access-static-property-or-method-in-jsp-via-el-3-0-jee7-tomcat-8
And if you note in the answer, it was also reported and fixed in the glassfish
implementation. javax.servlet.jsp api implements this functionality inside the
ScopedAttributeELResolver class after an attribute is not found. I've verified
this to be true in the current 2.3.2-b01 source code. However I think they
might have forgot to call resolveStatic also.
I'm going to make another bug post for an ImportHandler issue that if this is
implemented may also effect the functionality.
--
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
