While migrating some of my work stuff from my old WinXP laptop (ThinkPad T500... good old machine) to my new Windows 7 T430 (also fine iron), I switched from Tomcat v5 (yes, indeed, old) to Tomcat v7.
Tomcat v7 comes with a new servlet, JSP and EL spec. Not a real problem - I thought.
But once I got all the data sources etc up and running, my JSPs would not compile and gave EL parsing errors like "javax.el.ELException: Failed to parse the expression".
A bit googling revealed this nice post on Stackoverflow.
Turns out, that with the new EL standard, Java keywords are forbidden as variables.
And I had "static" as an URL parameter in ${empty param.static} as well as "class" as a variable to hold css/style class-names.
Once I renamed those everything worked fine again.
The first once was nasty, though, because as an URL parameter the name was of course exposed externally... Had to change some other scripts as well.
Tomcat v7 comes with a new servlet, JSP and EL spec. Not a real problem - I thought.
But once I got all the data sources etc up and running, my JSPs would not compile and gave EL parsing errors like "javax.el.ELException: Failed to parse the expression".
A bit googling revealed this nice post on Stackoverflow.
Turns out, that with the new EL standard, Java keywords are forbidden as variables.
And I had "static" as an URL parameter in ${empty param.static} as well as "class" as a variable to hold css/style class-names.
Once I renamed those everything worked fine again.
The first once was nasty, though, because as an URL parameter the name was of course exposed externally... Had to change some other scripts as well.
1 comment:
Post a Comment