Hello Konstantin Kolinko,
Thank you for the useful debugging tips. By setting the server in Strict
Compliance, I found some problems with our TLD declarations. After fixing
that, isELIgnored has the default of true, as expected.
Thanks again!
Sincerely,
Stephen McCants
On Sat, 8 Nov 2014
Hello Christopher Schultz,
Sorry for the delayed reply.
On 11/7/14 2:51 PM, Stephen McCants wrote:
I'm seeing a strange problem where isELIgnored has the wrong
default value for a new Tomcat install of 5.0.56.
That version number is certainly wrong.
Highest 5.0 version is 5.0.30
I worked around the problem by adding the following to the JSP
files:
%@ page isELIgnored=false %
However, I'd like to understand where the configuration error is
occurring as from my perspective nothing changed except OS and
Tomcat version. My own efforts have turned up nothing helpful
Hello All,
I'm seeing a strange problem where isELIgnored has the wrong default
value for a new Tomcat install of 5.0.56.
I'm moving a Web Application on Windows 7 to Windows 2008 and that
caused the EL expressions to stop being evaluated on the new install..
Problem is only seen on Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stephen,
On 11/7/14 2:51 PM, Stephen McCants wrote:
I'm seeing a strange problem where isELIgnored has the wrong
default value for a new Tomcat install of 5.0.56.
That version number is certainly wrong.
Highest 5.0 version is 5.0.30
Highest 5.5
