Jump to content
We've recently updated our Privacy Statement, available here ×

IT just doesn't work!


patricksand

Recommended Posts

Okay...I backed out of 1.3.2 to 1.3.1 and can at least create reports...but when I try to compile or run them (PDF Preview, for example) from a live source (a database connection that works fine)...I get the following:

 

Compiling to file... .classic_landscape.jasper -> C:Program FilesJasperSoftiReport-1.3.1classic_landscape.java

Error compiling the report Java source.

java.lang.NoClassDefFoundError: org/apache/commons/digester/Digester at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:107) at it.businesslogic.ireport.IReportCompiler.run(IReportCompiler.java:535) at java.lang.Thread.run(Thread.java:595)

Compilation running time: 32

 

Sure looks like a classpath problem but I don't see how, since I specifically include the digester jar in my %CLASSPATH%

 

Environment is Windows XP and I just don't get it. I've checked through the forums, google, and what not and found nothing useful...

 

Here's what I've got set up: (let me know if you need any other info)

 

I'm running Java 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05),

 

I've set JAVA_HOME to d:SunAppserverjdkjre (where the Java SDK is located)

 

my classpath is set to:

 

d:SunAppserverlib;d:SunAppServerjdkjrelibextjasperreports-1.3.1.jar;c:

Program FilesJasperSoftiReport-1.3.1libcommons-digester-1.7.jar;c:Sybasej

Connect-5_5classesjconn2.jar;c:SybaseJconnect-5_5classes;d:SunAppServerj

dkbin;c:sybaseASEPMonclass.zip;c:sybaseASEP3pclass.zip;c:sybaseASEP_Win

323pclass.zip;c:sybaseASEP_Win32monclass.zip;C:NOTESLUTSCLASSES;.;C:PROG

RA~1IBMSQLLIBjavadb2java.zip;C:PROGRA~1IBMSQLLIBjavadb2jcc.jar;C:PROGR

A~1IBMSQLLIBbin;C:PROGRA~1IBMSQLLIBjavadb2jcc_license_cisuz.jar;C:PROGR

A~1IBMSQLLIBjavadb2jcc_license_cu.jar;C:PROGRA~1IBMSQLLIBjavacommon.jar

 

I also used the ClassPath option in the iReport tool and have set it to the jasperreports jar, the bean, and two commons jars (including the digester). So we should have things covered six ways from Sunday, right? But still I get a "can't find digester" error...

 

If I don't get some help soon, I'm going to tell my manager that this product is just too twitchy to use in a production environment and we need to stick with our existing product (that we pay for). Sorry, but we can't have a multi-billion dollar company fail on reporting obligations because a product is twitchy.

Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

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...