By: dkamp - ibmskippy JasperCompileManager.compileReportToFile() 2006-02-22 19:25 When attempting to use either JasperCompileManager.compileReportToFile() or JasperCompileManager.compileReport() I get the following run time errors (no compiler issues) : package net.sf.jasperreports.engine does not exist import net.sf.jasperreports.engine.*; package net.sf.jasperreports.engine.fill does not exist import net.sf.jasperreports.engine.fill.*; Any help would be appreciated. I am using WebSphere Application developer 5.1.2 and have imported the following jar versions: jasperreports-1.2.0.jar commons-digester-1.7.jar common-beanutils-1.7.0.jar itext-1.3.jar (not sure if needed) By: Denny Valliant - xenden RE: JasperCompileManager.compileReportToFile( 2006-02-22 20:17 Ah the bane of Java people everywhere, the dreaded classpath issue. For some reason WebSphere isn't finding the Jar files for jasperreports. Are you sure you have them in the right location? XD By: Scott Resnik - scottresnik RE: JasperCompileManager.compileReportToFile( 2006-02-28 06:37 I'm getting a similar result on websphere. Not using WSAD though. My app works fine on Tomcat and Jboss, but not on websfear. I have the jasperreports jar in the WEB-INF/lib, and am not setting any jasper properites. By: Denny Valliant - xenden RE: JasperCompileManager.compileReportToFile( 2006-02-28 18:14 Still sounds like a classpath problem. They can be bothersome at times but are solveable with a little investigation. Can you check your class path from your app and see that it includes the correct directories? Another option is setting the class path from the app, but I'd recommend figuring out how websphere wants you to handle adding jars and such for your applications. If it's anything like JRun, it can be deceptive as the server has a web-inf and the sub-servers have web-inf's as well. Poke around and see... May the Force be with you! XD
2006 IR Open Dicussion's picture
Joined: Aug 10 2006 - 3:24am
Last seen: 8 years 9 months ago

0 Answers:

No answers yet