-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"error-on-el-not-found" behavior is not as specified #9537
Comments
This seems to be entirely within the Apache Jasper implementation. |
jetty-12.0.x for ee10 is currently using Apache Jasper 10.1.5. The latest released version is 10.1.7. There have only been 2 updates to anything jasper related since 10.1.5, see: https://tomcat.apache.org/tomcat-10.1-doc/changelog.html. Namely issues https://bz.apache.org/bugzilla/show_bug.cgi?id=66419 and https://bz.apache.org/bugzilla/show_bug.cgi?id=66441. @opengl-8080 do either of those sound like they're related to this issue? |
@opengl-8080 thanks for this report: I found the problem. We didn't support parsing the |
I have installed |
Fixed via #9625 |
Jetty version(s)
12.0.0.beta0
Java version/vendor
(use: java -version)
OS type/version
Windows 10
Description
In the specification of
error-on-el-not-found
added in Jakarta Server Pages 3.1, it is stated that if botherror-on-el-not-found
anderrorOrELNotFound
are not specified,ELResolver
returnsnull
.3.3.4. Unknown EL Identifiers
However, when using Jetty 12.0.0.beta0,
PropertyNotFoundException
is thrown even if the above condition is met.The following is a detailed summary of how Jetty behaved depending on the settings, using the reproducible project attached to this issue.
unspecified
injsp-property-group
refers to a state where thejsp-property-group
tag does not exist inweb.xml
. Also, the state wherejsp-property-group
isspecified
anderror-on-el-not-found
isunspecified
refers to a state where thejsp-property-group
tag exists inweb.xml
but theerror-on-el-not-found
tag does not exist. For example, the following state.I think that the part with (*) in RESULT is different from the specification.
Also, the results of verifying the same source code by deploying it to Tomcat 10.1.7 are as follows:
issue.How to reproduce?
reproduce.zip
I have attached a small Maven project that reproduces the issue.
The initial configuration sets
jsp-property-group=specified
,error-on-el-not-found=unspecified
, anderrorOnELNotFound=unspecified
.You can reproduce the issue by launching the application with
mvn jetty:run
and accessinghttp://localhost:8080/
.You can verify other patterns by adjusting
src/main/webapp/index.jsp
andsrc/main/webapp/WEB-INF/web.xml
.The text was updated successfully, but these errors were encountered: