I'm not sure if my problem is related to JasperReports-JSF or Tomcat but I'd
like to know what you folks think.
I have a JSF2.0+JPA2.0 (Java EE 6 Web) project running in Tomcat 7. When I add
the JAR files from lib/ directory of JR-JSF archive, Tomcat refuses to deploy
the application. Below is the Tomcat log:
Jul 14, 2011 3:17:03 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class
I know that JR-JSF doesn't work with JSF2 yet but the stacktrace makes me
think that there is some other issue rather than JSF2; perhaps a silly deploy
mistake on my side? Please let me know if you need more information to crack
I'd appreciate any help/idea. TIA.
PS: Using 1.0-beta4
Well, last JR-JSF beta version should work better with JSF2 than previous ones
since now plugin's lifecycle has been aligned with JSF lifecycle.
Anyway, as you've stated, this is not an issue related with JSF2 but a class
loading one. It looks too weird since if Tomcat tried to load
net.sf.jasperreports.jsf.config.ConfigurationStartupListener class it's
because it could load the tag library definition bundled with the JAR file
(it's there where that listener is configured).
To help me understand the issue, would you be so kind to post here snippets
from your web.xml and a list of the dependecies packaged with your WAR file?
Hi there Alonso,
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="[url]http://java.sun.com/xml/ns/javaee[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]" xsi:schemaLocation="[url]http://java.sun.com/xml/ns/javaee[/url] [url]http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd[/url]">
Derby JDBC driver
One thing that might be connected to this: when I add the JR-JSF namespace to
index.xhtml NetBeans complains that "No library found for this namespace".
Thanks for the information, I was expecting you having configured the TLD file
at web.xml but your last paragraph gave me the clue!
I found a mistake in project's documentation. Tag library has changed from
previous beta versions, new namespace should be:
Will have the "getting started" page updated as soon as possible. Sorry again
mmm, well, last statement should fix the problem about netbeans blaming the
missed namespace, but having a more deep thought, the missed class should be
loaded anyway since jar file is in the classpath!
By any means I try to reproduce the problem I can't get it. I tried to startup
a Tomcat 7 with JSF 2.0, Spring 3.0.0 and Hibernate 3.5.x and mine seems to
start perfectly (I just mean start, as you know support for JSF 2.0 is beyond
this current version and should be considered experimental). Anyway, I can
read following message at Tomcat log files:
JRJSF_0023: JasperReports JSF Plugin initialized.
I would like to have a follow up about this issue, did you get any further or
still stuck at the same problem?
Now I'm back at my laptop (had a short weekend journey).
Thanks for the update on tag library it fixed the NetBeans errors. But no more
luck. I thought it might be my project configuration or some configuration
problem with Tomcat; so created a new JSF2.0 project without JPA or any other
library, added JR-JSF libraries to the project and tried to run it on Tomcat
and the same happened.
Now comes the funny part: I even created a JSF1.2 project, added JR-JSF
libraries to the project and it didn't deploy either! I also tried with
copying JR-JSF jar file to Tomcat lib/ but no luck. And creating projects with
different Java EE versions (5 or 6) made no difference.
At least now we can be sure it's not related to JSF version at all :-)
Yep, it's not about JSF version... I tried a new deployment with less
dependencies on Tomcat 7 and faced the same issue whilst deploying same
artefact at Tomcat 6 worked !! Can't understand a so weird behaviour...
I filed a bug about this in Tomcat's bug database, hope receive a response
Sorry for not being able to give more help about this...
I'll monitor the issue you just filed. Thank you for your time and patience.
After some discussion about this issue with the guy from Tomcat development
team I eventually acknowledged the issue, I filed a bug in SF's database which
can be found at URL:
By the way, I also solved the mistake at the documentation in page "Getting
Started" and the broken link to the TLD Documentation.
P.S.: I'll avoid make any comments about how Tomcat deals with TLD definitions
from version 7 and later... ;)
Thanks for your efforts.
I noticed that the issue is now fixed and closed. Is it applied to 1.0-beta4
too or just to the trunk?
Since it was a very annoying issue that prevented the library to properly work
I applied the patch to 1.0-beta-4 branch and trunk. So current download for
1.0-beta-4 should work. Haven't commited changes in SVN though 'cos I did the
fix late at home and forgot that step, it will be updated as soon as possible.
Tested the new binary (beta4) and it deploys alright. Thank you.
Log in to post a comment.