https://bz.apache.org/bugzilla/show_bug.cgi?id=64872
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
Fudging the spec is not an option. Providing an option that provides non-spec
compliant behaviour and is disabled by default is an option.
That said, I do wonder why expression language is being used in these instances
rather than a scriptlet.
<my:tag enumProperty="<%= hotFudge %>"/>
rather than
<my:tag enumProperty="${'hotFudge'}"/>
should give you exactly the behaviour you desire shouldn't it?
I'd also expect it be possible to implement with some form of global search and
replace. That approach strikes me as a rather less risky solution (both from an
implementation point of view and a testing one) than an optimisation in the JSP
compiler. It also means you would not be reliant on a Tomcat specific
performance tweak should you decide to switch containers at some point.
--
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
