That is Step 2 in the 3-step process I want to avoid:
1. Upgrade iReport.
2. Upgrade the files in Tomcat's common directory (i.e., copy the JAR
files).
3. Restart Tomcat.
This is what I would like to do (that I have a working solution for, by the
way, but involves setting the CLASSPAT
Then iReport no longer works.
Dave
Hi,
Setting *shared.loader* in catalina.properties is a nearly perfect solution.
Thank you.
One minor, but significant, technical issue remains: iReports ships with a
JAR file (jdt-compiler-3.1.1.jar) that conflicts with a JAR file shipped
with Tomcat (ecj-3.6.jar, if memory serves).
Can I add t
Hi,
> In the first case, multiple applications using JasperReports
> > will result in a gross waste of resources
>
> I would categorize it as a trivial waste of resources. Have you checked
> the price of disk and RAM lately?
>
Sure. The machine has 8 GB of RAM. 7 GB used by the (100 GB) PostgreS
Hi,
The iReport tool (and hence JasperReports) bundles scores of JAR files
across two different directories. (One of these JAR files conflicts with a
JAR file deployed by Tomcat.)
For development purposes it makes sense to have Tomcat and iReport installed
on the same machine. This poses a mainte
