Jump to content
Changes to the Jaspersoft community edition download ×

Error after update to 6.2.2


Recommended Posts

I don't use Maven so I just put the

  • jasperreports-6.2.1
  • jasperreports-fonts-6.2.1
  • jasperreports-functions-6.2.1
  • jasperreports-javaflow-6.2.1

in the build path and it was ok until 6.2.1 after I replace with 6.2.2 jars I got some problems:


Exception handling request to /saidaoPublico.faces: javax.servlet.ServletException: org/apache/batik/bridge/UserAgent
java.lang.NoClassDefFoundError: org/apache/batik/bridge/UserAgent

https://gist.github.com/erickdeoliveiraleal/ddd588ecfb7d9e1c38f14af935fe1578

I already filled a issue but no developer answered.

http://community.jaspersoft.com/jasperreports-library/issues/7416

Link to comment
Share on other sites

  • Replies 4
  • Created
  • Last Reply

Top Posters In This Topic

JasperReports requires some other libraries when using some features. If you open up "ivy.xml" with a text editor, you'll be able to see a list of third party libraries used by JasperReports. Search for "batik". You're missing "batik-bridge-1.8.jar" but you'll probably need other "batik*" libraries too.

JasperReports also requires libraries such as "commons-collections", "commons-digester", and "commmons-beatutil". If you don't want to use maven or ivy, you'll have to manually download these files and put them in the class path.

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

I have the same problem with v6.2.2 using Eclipse and Maven:

java.lang.NoClassDefFoundError: org/apache/batik/bridge/FontFamilyResolver

java.lang.ClassNotFoundException: org.apache.batik.bridge.FontFamilyResolver

I use batik* in v1.7.

 

I use a POM with following dependencies:

jasperreports-6.2.2
jasperreports-fonts-6.2.2
jasperreports-functions-6.2.2
com.lowagie:itext:2.1.7

Fonts and Functions were manually downloaded from this website and put in an own repository, because I could not find Fonts > v6.0.0 in public repositories.

EDIT:

I have the same error with the 6.3.0 libraries.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...