Matt Jones: "There were one more strict changed to be true between 5.5 & 7.0 org.apache.jasper.compiler.Parser.STRICT_WHITESPACE (If false the requirements for whitespace before an attribute name will be relaxed so that the lack of whitespace will not cause an error. Default is the spec value which is true)
Perhaps because the code isn't <%@ include or using <jsp:include there it's causing an error now?"
Confirmed: we no longer use the strict whitespace setting on any qa server
Sam Ottenhoff November 7, 2011 at 5:40 AM
There should be no need to use the STRICT_WHITESPACE workaround starting with 2.9.0A02. Please re-open this ticket if any problems are found with whitespace errors in JSPS.
Thanks Aaron.
Aaron Zeckoski November 4, 2011 at 7:31 PM
I am not seeing anymore errors at the moment so I am going to say yes, I think we can close it
Add the following JAVA_OPTS setting to the release notes for 2.9:
-Dorg.apache.jasper.compiler.Parser.STRICT_WHITESPACE=false
At least one JSF tool (forums) requires it when running it in Tomcat 7.
http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html
Matt Jones: "There were one more strict changed to be true between 5.5 & 7.0 org.apache.jasper.compiler.Parser.STRICT_WHITESPACE
(If false the requirements for whitespace before an attribute name will be relaxed so that the lack of whitespace will not cause an error. Default is the spec value which is true)
Perhaps because the code isn't <%@ include or using <jsp:include there it's causing an error now?"
Matt's suspicion was confirmed by David Horwitz.