John Quinn wrote:
I am taking the value of external xml entities.
I suppose you mean you *didn't* do this.
I would like to note that I'm getting the following warnings on the systems
that it does run on:
[WARNING] table-layout=auto is not supported, using fixed!
That's warning warning you
I have already pushed the xml into a file and performed the xslt on the Redhat2.1 box that gives me the headache. I've run FOP command line and it output the expected PDF file. It just doesn't work under JBoss. It's using the Xerces implementation (which is in the JBoss endorsed library) currentl
John Quinn wrote:
The xml has no '&' in it. It is formed directly from data that is extracted
from the database.
Well, experience tells that database content is the most common
source of trouble like unescaped ampersands. But you're right,
the error message says indeed the problem is with the
The xml has no '&' in it. It is formed directly from data that is extracted from the database.
Why I am focused on the xsl is due to the fact that it dies on this line:
at com.icl.saxon.PreparedStyleSheet.prepare(PreparedStyleSheet.java:119) at com.icl.saxon.TransformerFactoryImpl.newTemp
John Quinn wrote:
Okay, saxon is now running under JBoss. I still fail at the same line with
the following error now:
...
13:57:58,406 INFO [STDOUT] Error on line 37 column 81 of null:
Error reported by XML parser: The entity name must immediately follow the
'&'
in the entity reference.
..
Okay, saxon is now running under JBoss. I still fail at the same line with the following error now:
13:57:58,102 INFO [PDFReport] PDFReport code source for TransformerFactory: (file:/opt/opensource/jboss-4.0.3SP1/server/test1/tmp/deploy/tmp14491teaa.war/WEB-INF/lib/saxon.jar )13:57:58,103 INFO [
I found it on saxon.sourceforge.net:
Saxon 6.5.4 dropped support for certain rarely-used features of Saxon 6.5.3, notably support for JDK 1.1 and the Microsoft Java VM, support for FOP integration, and the applet interface. Users requiring these features should continue to use
version 6.5.3.
I'
Where did you find something that says only SAXON 6.5.3 is compatible
with FOP? FOP should work fine with any XML Parser and XSLT
implementation as long as it implements the JAXP API and does not have
any strange bugs. You can also try to force SAXON to use Xerces by
setting the "javax.xml.parsers.
I have tried using Saxon, but the application throws a config exception at that point because the commons digester must check for a validating parser and it say the aelfred sax parser implementation is not such a parser (packaged with Saxon
6.5.3):
javax.xml.parsers.ParserConfigurationException: A
For clarification, xml_apis.jar is the correct name of the duplicate jar file that I took out of my war file and then had the admins redeploy the new war file to JBoss.
I should add that there are no endorsed jars in the JRE under the JAVA_HOME/lib/endorsed directory. In fact, there is no endorse
Hmm, you asked for ideas. Not sure if they help:
- JBoss seems to have a lib/endorsed directory. It may be worthwhile to
experiment a little there: remove, change
- Try replacing Xalan-J with SAXON if only to determine if there's
something else playing into this.
Good luck!
On 21.03.2006 22:0
I did find an extra xmlapi.jar in my war file. However, none of the other endorsed libraries in JBoss are in my war. I have had the admins deploy the new war to JBoss in the Redhat 2.1 environment and still get the same error on the same line of code.
This problem is keeping us from going to p
Make sure you don't have multiple xalan.jars in your environment. In
JDKs 1.4 or later no XML parser nor XSLT implementation should show up
in WEB-INF/lib directories or in normal lib directories. Rule of thumb:
The implementation JARs for XML parsers (ex. Xerces) and XSLT
implementations (ex. Xala
Okay, I ran fop using the command line with sample files built with the servlet in the windows environment in the Redhat 2.1 environment using the xalan jar from the endorsed library in JBoss 4.0.3SP1. It ran just fine.
Any ideas from here?
Thanks
John
On 3/20/06, Andreas L Delmelle <[EM
On Mar 20, 2006, at 21:24, John Quinn wrote:
H,
I am receiving an exception when I try to generate a PDF in a
Servlet using FOP under JBoss4.0.1SP1 (and JBoss4.0.3SP1) in a
Redhat linux 2.1 OS.
I am running the same code under a Suse linux and Win XP OS
without any errors using JBoss.
I am receiving an exception when I try to generate a PDF in a Servlet using FOP under JBoss4.0.1SP1 (and JBoss4.0.3SP1) in a Redhat linux 2.1 OS.
I am running the same code under a Suse linux and Win XP OS without any errors using JBoss.
Here's the Exception:
2006-03-02 15:17:21,969 INFO [STD
16 matches
Mail list logo
