Hi Kevin,
Your XSL-FO appears to be trunkated.
You should have a look in your XSLT stage.
For further inverstigation, you should describe your server environment:
- JVM used
- platform
- XSLT processor (if any)
- etc.
I don't understand why postprocessing has any effect during the FO
Pascal,
Thanks for getting back. Here are the environment details:
- FOP 0.94
- Websphere 6.0 server
I do not have any idea as to where to start from to resolve this error. My
requirement needs some post processing before rendering the final PDF, so I
create the Area Tree first and then apply
Pascal,
Sorry, I didn't provide the complete details of the server environment FOP is
running:
- FOP 0.94
- Websphere 6.0 Application server
- Windows 2003
- Xerces/Xalan
- Fop is embeded in Java
Thanks
kevin
-
To
Hi François,
sorry for digging up this old topic again, but I face exactly the same
problem now and it might be really helpful if you could tell me how you
solved it.
I updated my application from FOP 0.93 to 0.94 recently and everything
worked fine. I kept using Xerces 2.6.2 as another resource
Hi,
Reading your Log messages (endElement Mismatch: table-cell), I guess end tags
are missing to these elements.
This is why I said that your FO is trunkated.
Can you check that in your server environment?
If that is the case, I suspect there is something wrong with XML in Webserve.
There
Hi
I'm having again a problem of page breaks and keeping things together (I
last wrote to this list in June 07).
I have a paragraph with a title and a body afterwards that must be kept
together if possible. As a fix to my last problem, I check whether the
title and body should be kept together
Eric,
You should use keep-with-next on title (or keep-with-previous on 1st para),
that should do the trick.
Pascal
Message d'origine
De: Lewis, Eric [mailto:[EMAIL PROTECTED]
Date: mer. 19/09/2007 16:33
Hi
On Sep 19, 2007, at 11:04, Kevin wrote:
Hi
Sorry, I didn't provide the complete details of the server
environment FOP is
running:
If you say that 'the same XSL works fine in your development
environment', does that also mean 'the same XML'? Can you check with
the *exact* same XML +
