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 17:08:46 +0300 Konstantin Kolinko <knst.koli...@gmail.com> wrote: > >> 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 or > >> illuminating. > >> > >> Where should I be looking in the configurations for a difference? > >> What differences would come into play? > > > > What is your tag library declaration in your JSP file? That's probably > > the most important thing, here. Are you supplying your own version of > > JSTL, EL, etc. along with your web application? > > > > +1. There have been several user reports when Apache Maven packed > conflicting API implementation jars into a war file. I do not remember > it resulting in such symptoms, but things were going awry for those > affected. > > I would suggest trying the following: > > 1) Add logEffectiveWebXml="true" to your Context and see how that > web.xml is actually interpreted by Tomcat (considering all web > fragments and annotations) > http://tomcat.apache.org/tomcat-7.0-doc/config/context.html > > 2) Run in "strict servlet compliance" mode. That will enable > validation of your web.xml against schema. > > http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html#Specification > > 3) Are there any errors, warnings in the log files? > > > If that does not help, then maybe > a) inspect the java code generated for your JSPs > > b) run with a debugger > https://wiki.apache.org/tomcat/FAQ/Developing#Debugging > > c) try with 7.0.42 on Windows, and then with intermediate versions up > to 7.0.56 to see when the problem appeared. > > d) test with 7.0.57 (a release candidate is currently in the voting > process on dev@) > > e) simplify your web application until you have a reproducible test > case that you can show others > > The examples webapp has EL on its pages and those are certainly working. > > f) update you web.xml to version 3.0 and configure it to avoid > annotation scanning > https://wiki.apache.org/tomcat/HowTo/FasterStartUp > > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > ---------- Stephen McCants Senior Software Engineer Healthcare Control Systems, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
