Possible user code changes required when we upgrade to Tomcat 6.0.18

2008-08-14 Thread Donald Woods
This is a notice to developers and users - I've run into several JSP files in our build (mainly the monitor webapp) that require code changes to work with Tomcat 6.0.18, due to tightened code around the JSP 2.0 spec in Jasper during the Tomcat 6.0.17 release. The build errors look something l

Re: Possible user code changes required when we upgrade to Tomcat 6.0.18

2008-08-15 Thread Jarek Gawor
Donald, The console testsuites are failing. I'm seeing the following exception on a number of different portlets in the console: 11:49:49,298 ERROR [[JMSWizard]] Servlet.service() for servlet JMSWizard threw exception java.lang.ClassCastException: java.lang.NullPointerException at org.ap

Re: Possible user code changes required when we upgrade to Tomcat 6.0.18

2008-08-15 Thread Donald Woods
Yep, I'm looking at it. Thanks for mentioning it on the list. -Donald Jarek Gawor wrote: Donald, The console testsuites are failing. I'm seeing the following exception on a number of different portlets in the console: 11:49:49,298 ERROR [[JMSWizard]] Servlet.service() for servlet JMSWizard

Re: Possible user code changes required when we upgrade to Tomcat 6.0.18

2008-08-17 Thread Donald Woods
Think I'm making progress If I upgrade the 2.1 branch to 6.0.18 and build, I get compile time errors which don't show up with trunk builds - [INFO] [ERROR] FATAL ERROR [INFO] ---

Re: Possible user code changes required when we upgrade to Tomcat 6.0.18

2008-08-18 Thread Donald Woods
For the new spec compliant escape quoting behavior, users can enable the prior support in Tomcat by setting - org.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false http://www.nabble.com/svn-commit%3A-r685823---in--tomcat%3A-container-tc5.5.x-webapps-docs-config-systemprops.xml-current