Summary: | Behaviour of ResourceBundleELResolver | ||
---|---|---|---|
Product: | Tomcat 6 | Reporter: | b.diedrichsen |
Component: | Jasper | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 6.0.35 | ||
Target Milestone: | default | ||
Hardware: | PC | ||
OS: | Linux |
Description
b.diedrichsen
2012-03-29 09:41:39 UTC
Tomcat is no longer following the EL spec. The behaviour prior to the fix for bug 46915 was correct. I'm not sure it is possible to fix bug 46915 and be specification compliant. I'll revert the fix for bug 46915, put together some test cases and see what I can come up with. Depending on how well things go, bug 46915 will either stay as FIXED or be changed to INVALID. Thanks for the quick reply. I did not check the spec so wasn't aware that the current behaviour actually violates the el specs. Why was the fix for bug 46915 done in the first place? Did the specs change from then to now? Anyways, keep up the good work. Tomcat is an impressive and very reliable product. No change in the spec. I failed to check the EL spec before I fixed bug 46915. If I had, that would have been resolved as INVALID. It looks like EL 2.2 (Tomcat 7) has some new features that would allow the requirement in bug 46915 to be met. Time to write some unit tests. Fixed in trunk and 7.0.x and will be included in 7.0.27 onwards. The fixed has been proposed for 6.0.x. Thank you Mark, this was really a quick resolution of the issue. |