Well, the latest Xalan ( 2.5.1 ) is in place, and when I run its
EnvironmentCheck, everything seems to be ok (in fact, even more than ok, but
maybe this is just a gimmick from the Xalan-developers :-) ). So this
already works.
The problem itself isn't solved though... I made the transformation with
Xalan, to have a look at the intermediate .fo, and now at least I see what's
causing the exception.
Here's a short description :
think of the xslt as a template for payslips, and it should produce a single
pdf per employer (or per group of employees)
the xml contains the employer data and some general info (once) and the data
from each employees' salary, and I have it structured like :
<employer ref="999999">
<name>...</name>
<addr>...</addr>
...
</employer>
<general>
<date-printed>14-08-2003</date-printed>
... [ some other info ]
</general>
<employee ref="0000001">
<name>...</name>
...
</employee>
<employee ref="0000002">
<name>...</name>
...
</employee>
Now, what happens is that the data from the employer-element and the
general-element appear untagged in the .fo, right between the <fo:flow> and
the first <fo:block> (actually it's a <fo:table>). The rest of the .fo seems
to be quite correct and ready to be fed to fop.
It's very likely that the problem would solve itself if I redesigned the
xslt and dtd, but it remains curious that this structure worked just fine on
win2k...
Another weird detail (maybe there's a perfectly valid explanation): although
the xslt and xml have the "ISO-8859-1" encoding, the resulting .fo is
"UTF-8"-encoded.
The search continues...
Cheerz,
Andreas Delmelle
-----Original Message-----
From: J.Pietschmann [mailto:[EMAIL PROTECTED]
Sent: donderdag 14 augustus 2003 1:17
To: [EMAIL PROTECTED]
Subject: Re: FW: Annoying 'ArrayIndexOutOfBoundsException'? - Progress??
Andreas L. Delmelle wrote:
> ( I have a vague feeling it will turn out to be a ridiculously small
detail
> I've overlooked, so I'll definitely share it with you guys - if I succeed
in
> finding it... ;-) )
>
Google a bit for something like "Java endorsed libs".
Look where your JRE stores the big RT jars (like, ahem, rt.jar).
Check $JAVA_HOME/lib first. Create a directory called 'endorsed'
there, unless it already exists. Grab the newest Xalan jar
and put it there. You should be set, if Apple followed the same
architecture as Sun. If this isn't the case, check your JVM's
docs on how to add a jar to the bootclasspath, and apply this
to said newest Xalan jar.
On most lists dealing with Java+XSLT this is a VFAQ. I think
the Cocoon docs have a quite extensive treatment.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
