My build of FOP from 2004/05/29 works fine on Sun Java 1.4.1_02 with
Tomcat 5.0.19, but when I move toSun Java 1.5.1 and Tomcat 5.5.7 I get
the URI I/O error listed below. This build included a Batik.jar with
files dates 10/11/2003.
The exception message below seems to indicate it is choking on
You're asking for something to work that was written before JDK 1.5 was
out. 1.5 has some serious consequences. Not everything is guaranteed to
continue working. BTW, are you sure you mean 1.5.1 or rather 1.5.0_01
which is the latest version? Just keep in mind that due to these bigger
changes it
Manoj:
Try to load your fonts without the userconfig.xml file and see if it works
(change were necessary):
//config fonts
Vector allFonts = new Vector();
Vector allTrips = new Vector();
//name weight style
allTrips.add(new FontTriplet(MS Song,normal,normal));
Jeremias,
You are correct - java version 1.5.0_01. And yes I know it is still
very new.
I needed session replication with Tomcat 5.5.7 and Java 1.5 was
recommended (there is a mode that works with Java 1.4 also).
Thank you for the API reference I will take a look.
- Richard
-Original
James,
Thanks for the input and suggestion. I installed the Java 1.4
compatibility files for Tomcat 5.5.7 and reverted to Sun Java 1.4.2_03.
I still get the error below :(
The good news is I know more - it does not appear to be a Java 1.5
issue, but possibly a Tomcat 5.5.x issue.
Any additional
Kumar:
Victor answered my similar question last month (snipped below).
Louis.Masters wrote:
In order to get around some memory issues, I am creating
multiple page sequences on my reports. The problem is, every
time a new page sequence is created, a new page is created.
Is there any way I
Thanks Victor for your response. So did you have any alternate approaches to
resolve this issue in your application?
Thanks,
Kumar Puppala
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2005 11:03 AM
To: [EMAIL PROTECTED]
Subject: Re:
Richard Mixon (qwest) wrote:
I checked my SVG markup and am not sure how I would change this as I'm
using an xlink:href. Here is an example:
xlink:href=images/allTimeBest/c:out
value=${cmSummary.allTimeBestIcon}/
This means that it is using the base URL for the document
to resolve the
Thomas DeWeese wrote:
Richard Mixon (qwest) wrote:
I checked my SVG markup and am not sure how I would change this as
I'm using an xlink:href. Here is an example:
xlink:href=images/allTimeBest/c:out
value=${cmSummary.allTimeBestIcon}/
This means that it is using the base URL
Bingo! That was it. I changed it from file:// to file:/// and all
works now. You earlier mentioned that might be it - but I was so focused
on the fact that it worked on Java 1.4.1 that I figured I had it
correctly.
That is weird though that moving past Java 1.4.1 breaks this.
Thank you once
Kumar Puppala wrote:
Thanks Victor for your response. So did you have any
alternate approaches to resolve this issue in your application?
That depends on what you mean by performance issue. If you have plenty of
memory, I don't think your performance speed will be adversely affected by
using
11 matches
Mail list logo
