Thanks. I'm moving forward to 7.0.35 with the patch, whereas without
the patch 7.0.35 would have been a non-starter (not because it's that
bad but rather because 7.0.34 was good enough that this issue, if
unresolved, more than cancels out 7.0.35's fixes from my perspective).
On 1/17/2013 12:36 PM, Violeta Georgieva wrote:
2013/1/17 Jess Holle <je...@ptc.com>
As part of testing Tomcat 7.0.35 when I moved to it, I run an Ant script
to pre-compile all our JSP pages.
When doing so I get a huge number of new failures which boil down to the
following stack trace. Any ideas here? I can dig in to try to see what's
causing this, but this is new behavior.
Poking around in the running web app, things seem to work, so the issue
seems specific to using Jasper for pre-compilation.
[jasper2] java.lang.NullPointerException
[jasper2] at org.apache.jasper.compiler.**TagPluginManager.init(**
TagPluginManager.java:83)
[jasper2] at org.apache.jasper.compiler.**TagPluginManager.apply(**
TagPluginManager.java:57)
[jasper2] at org.apache.jasper.compiler.**Compiler.generateJava(**
Compiler.java:240)
Check this https://issues.apache.org/bugzilla/show_bug.cgi?id=54440
Regards
Violeta
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
