You've probably already checked, but in case not - have you had a look at the JasperReports pom? Perhaps there are dependencies it references that need to be explicitly excluded in your pom to stop interfering with your other project dependencies?
Regards, Jim. -----Original Message----- From: Rich [mailto:rich...@moremagic.com] Sent: 30 July 2010 15:01 To: Tapestry users Subject: Re: JasperReports / Chenillekit-reports documentation Thiago H. de Paula Figueiredo wrote: > On Wed, 28 Jul 2010 18:13:17 -0300, Rich <rich...@moremagic.com> wrote: > >> Hi, > > Hi! > >> java.lang.ClassNotFoundException >> org.apache.poi.hssf.usermodel.HSSFCellStyle > >> java.lang.NoClassDefFoundError: >> org/apache/commons/collections/map/LRUMap > > These are dependency problems, not Tapestry ones. The first one looks > like POI and the second one Apache Commons-Collections. > Sort of. The POI one is clearly a dependency problem and I stated as much, since it uses outdated versions of JasperReports. However, the second one regarding Apache Commons and LRUMap is something that is breaking in the Tapestry-Hibernate Module when all that's changed is the JasperReports dependency. I didn't fully explain this because it was fully detailed with the exception in an earlier e-mail in this thread I wrote. Caused by: java.lang.RuntimeException: Error invoking service builder method org.apache.tapestry5.hibernate.HibernateCoreModule.buildHibernateSessionSource(Logger, List, RegistryShutdownHub) (at HibernateCoreModule.java:123) (for service 'HibernateSessionSource'): org/apache/commons/collections/map/LRUMap at org.apache.tapestry5.ioc.internal.ServiceBuilderMethodInvoker.createObject(ServiceBuilderMethodInvoker.java:76) at org.apache.tapestry5.ioc.internal.OperationTrackingObjectCreator$1.invoke(OperationTrackingObjectCreator.java:45) at org.apache.tapestry5.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:68) ... 134 more Caused by: java.lang.NoClassDefFoundError: org/apache/commons/collections/map/LRUMap So there seems to be some transitive breaking there, which I would say puts it beyond just a dependency problem. Anyway, after much trial and error it turns out that Apache POI 3.2 and JasperReports 3.5.0 will get XLS working. Older JasperReport versions call deprecated POI methods, newer JasperReport versions break the Hibernate module, older POI versions have bugs that break runtime execution, and newer POI versions also break! Regards, Rich --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
