Hello Christopher,
Thanks for the reply. Actually not, I am working with out-of-the-box
Tomcat7 and Tomcat8 in this case. I wonder if any classloader changes
occurred in the last builds that could have affected this.
Thanks,
Neill
On Wed, Mar 25, 2015 at 5:44 PM, Christopher Schultz <
ch...@chr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Neill,
On 3/20/15 12:28 PM, Neill Lima wrote:
> As of today I figured out that the jasper.jar in Tomcat's \lib
> takes care of the task out of the box. I've tweaked my pom a few
> times, but I started fresh today and realized it. So no pom updates
>
Hello Chris,
As of today I figured out that the jasper.jar in Tomcat's \lib takes care
of the task out of the box. I've tweaked my pom a few times, but I started
fresh today and realized it. So no pom updates were necessary. Still I'm
getting this exception I mentioned in the earlier e-mail:
Caus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Neill,
On 3/20/15 4:58 AM, Neill Lima wrote:
> I have a existing WebApp that I'm planning to upgrade to Tomcat8
> (version 8.0.20 as of today). It is running stable in Tomcat7
> already for ages.
Great.
> Tomcat8 does not embed the JasperListener
Hello list,
I'm not sure if this the right place to ask, but here it goes...
I have a existing WebApp that I'm planning to upgrade to Tomcat8 (version
8.0.20 as of today). It is running stable in Tomcat7 already for ages.
Tomcat8 does not embed the JasperListener so I added it manually to my
pom
