Cannot find jar file in WEB-INF

[ten jones]

We are creating a web based reporting application that will utilize iReports, jasper and jrxml files. We successfully created the transfer objects and jasper files, however, when we compile the appication it cannot seemed to find the iText-2.1.7 (for PDF files) or poi.3.6 (for excel spreadsheets).

The .jasper and .jrxml files are found and the objects and creation methods work because we can successfully create the html and word document versions of the reports just fine. If the application could find the jars mentioned above, it would fix the failing PDF and Excel reporting types.

We have the jasper-compiler-jdt-5.5.9 sitting in the WEB-INF/lib folder with all of the other 'special' jar files.

Has anyone else worked with iReports creating PDFs and had this issue? I can provide the stacktrace if needed.

[Jesper de Jong]

So the problem happens when you compile (not: run) the application? It sounds a bit strange because from the rest of your message it looks like you actually can compile the app, but that something goes wrong when you run it.

It's a bit hard to tell you exactly where the problem is, because that depends on what your development and build environment looks like. What IDE are you using? How is the project set up? Are you using a build tool such as Ant or Maven, are you sure the build script is set up to pick up the libraries at compile time correctly?

You'd have to make sure that at compile time the right jar files can be found, but how you do that depends on your environment.

[ten jones]

Sorry let me give some more information.

The application compiles and runs correctly, that is not the issue. I am using jdeveloper and weblogic 11g to run the application on my computer. We are using EJB 3 as well.

When testing the application in IE, it throws the error "cannot find com.lowagie.text.Document" and etc. Lowagie is is the iText.Jar, but it is there.

In the code, I've even added a line "import com.lowagie.text.Document;" to make sure the IDE can see the jar and it does not throw an error.

It's all in run time where the error occurs.