Re: SAX, fopservlet and 0.20.2
J: Thanks - that clarifies it. The newer xalan did and, with the upgrade to the newer fop and the namespace fix, it is now working (although I had to rename my servlet from fop to fop.pdf to get the pdf output in IE). I now have to work on performance - my users don't like waiting 30min to and hour for their pdf reports. Thanks! -Lou J.Pietschmann [EMAIL PROTECTED] on 06/06/2002 16:00:59 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 [EMAIL PROTECTED] wrote: I am now testing using the glossary xml/xsl files in the example directory, but with the same results. It works fine from the command line, but NPE whenever I introduce the SAXResult or SAXSource. I'm starting to think it might be something with me environment. Also, if I stream it to a file using StreamResult, I can then take the resultant fo and use the Fop command line utility on that and it is fine. It is possible that it is a problem involving undeclared namespaces. GGet a recent Xalan or get Saxon (http://saxon.sourceforge.net) at run your stylesheet: xalan -in foo.xml -xsl foo.xsl -out foo.fo The Xalan included in the FOP distribution sometimes throws NPEs by itself and sometimes passes null namespaces to FOP which cause NPEs, but the latter might be masked by serialisation and reparsing. A more recent Xalan will provide a proper error message. Sorry, the xml.apache.org stated you needed the sax api, not sax.jar - xalan should cover this? Not Xalan, Xerces (included in the FOP distribution. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SAX, fopservlet and 0.20.2
OK, I take back some of what I previously said. I upgraded my xalan to 2.3.1 and that fixed the NPE when transforming the glossary example. I still consistently get the NPE on my own files from the servlet, but now I also get it from the command line. Being at a loss, per the xalan 2.3.1 instructions, I switched my xerces jar to xercesImpl.jar, but now I get the following: org.xml.sax.SAXParseException: The prefix fo for element fo:external-graphic is not bound. I am still using 0.20.2 fop so I am pretty confused on which jars I should be using. Anyone have any ideas? What jars should be in my path? -Lou [EMAIL PROTECTED] on 06/06/2002 07:51:09 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 J: Thanks for the response. I am now testing using the glossary xml/xsl files in the example directory, but with the same results. It works fine from the command line, but NPE whenever I introduce the SAXResult or SAXSource. I'm starting to think it might be something with me environment. Also, if I stream it to a file using StreamResult, I can then take the resultant fo and use the Fop command line utility on that and it is fine. Sorry, the xml.apache.org stated you needed the sax api, not sax.jar - xalan should cover this? If 0.20.3 is stable, I would consider upgrading - it's just that I have all the jar files frozen for at least another month. Thanks, Lou J.Pietschmann [EMAIL PROTECTED] on 06/05/2002 20:04:01 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 [EMAIL PROTECTED] wrote: I recently switched from a standalone FOP app to the servlet. The code compiles fine, but any lines that use SAX throw a transformer exception. Do your files work with the command line FOP? fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf If you get a NPE [ERROR]: null add the -d switch to get a stack trace. Also, I don't explicitly include the sax jar file - do I need to? I'm using xalan 2.0.0 and xerces 1.2.3. What sax jar file? You might also consider upgrading to 0.20.3. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SAX, fopservlet and 0.20.2
OK, I thawed the jar files and upgraded to 20.3 (and rolled back my xalan and xerces changes) and that seems to do the trick. The fo issue was a bug in an included stylesheet that I fixed. -Lou [EMAIL PROTECTED] on 06/06/2002 11:50:26 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 OK, I take back some of what I previously said. I upgraded my xalan to 2.3.1 and that fixed the NPE when transforming the glossary example. I still consistently get the NPE on my own files from the servlet, but now I also get it from the command line. Being at a loss, per the xalan 2.3.1 instructions, I switched my xerces jar to xercesImpl.jar, but now I get the following: org.xml.sax.SAXParseException: The prefix fo for element fo:external-graphic is not bound. I am still using 0.20.2 fop so I am pretty confused on which jars I should be using. Anyone have any ideas? What jars should be in my path? -Lou [EMAIL PROTECTED] on 06/06/2002 07:51:09 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 J: Thanks for the response. I am now testing using the glossary xml/xsl files in the example directory, but with the same results. It works fine from the command line, but NPE whenever I introduce the SAXResult or SAXSource. I'm starting to think it might be something with me environment. Also, if I stream it to a file using StreamResult, I can then take the resultant fo and use the Fop command line utility on that and it is fine. Sorry, the xml.apache.org stated you needed the sax api, not sax.jar - xalan should cover this? If 0.20.3 is stable, I would consider upgrading - it's just that I have all the jar files frozen for at least another month. Thanks, Lou J.Pietschmann [EMAIL PROTECTED] on 06/05/2002 20:04:01 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 [EMAIL PROTECTED] wrote: I recently switched from a standalone FOP app to the servlet. The code compiles fine, but any lines that use SAX throw a transformer exception. Do your files work with the command line FOP? fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf If you get a NPE [ERROR]: null add the -d switch to get a stack trace. Also, I don't explicitly include the sax jar file - do I need to? I'm using xalan 2.0.0 and xerces 1.2.3. What sax jar file? You might also consider upgrading to 0.20.3. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SAX, fopservlet and 0.20.2
[EMAIL PROTECTED] wrote: I am now testing using the glossary xml/xsl files in the example directory, but with the same results. It works fine from the command line, but NPE whenever I introduce the SAXResult or SAXSource. I'm starting to think it might be something with me environment. Also, if I stream it to a file using StreamResult, I can then take the resultant fo and use the Fop command line utility on that and it is fine. It is possible that it is a problem involving undeclared namespaces. GGet a recent Xalan or get Saxon (http://saxon.sourceforge.net) at run your stylesheet: xalan -in foo.xml -xsl foo.xsl -out foo.fo The Xalan included in the FOP distribution sometimes throws NPEs by itself and sometimes passes null namespaces to FOP which cause NPEs, but the latter might be masked by serialisation and reparsing. A more recent Xalan will provide a proper error message. Sorry, the xml.apache.org stated you needed the sax api, not sax.jar - xalan should cover this? Not Xalan, Xerces (included in the FOP distribution. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SAX, fopservlet and 0.20.2
[EMAIL PROTECTED] wrote: I recently switched from a standalone FOP app to the servlet. The code compiles fine, but any lines that use SAX throw a transformer exception. Do your files work with the command line FOP? fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf If you get a NPE [ERROR]: null add the -d switch to get a stack trace. Also, I don't explicitly include the sax jar file - do I need to? I'm using xalan 2.0.0 and xerces 1.2.3. What sax jar file? You might also consider upgrading to 0.20.3. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sax conflicts with tomcat-4.0.2-LE-jdk1.4
Jeremias Maerki [EMAIL PROTECTED] wrote: The only place where Xerces is directly imported is the PFMReader and TTFReader. Ok, Driver, when startet using the command line, uses Xerces by default, but nothing prevents you from using any JAXP parser with FOP. Stuff matching org.apache.x* in 0.20.2: ...Driver.java parserClassName = org.apache.xerces.parsers.SAXParser; ...PFMReader.java org.apache.xerces.dom.*; org.apache.xml.serialize.*; org.apache.xalan.xslt.*; ...TTFReader.java dto. ...fop.layout.hyphenation.PatternParser.java parserClassName = org.apache.xerces.parsers.SAXParser; ...fop.tools.anttasks.CompileXMLFiles.java parserClassName = org.apache.xerces.parsers.SAXParser; ...fop.tools.xslt.Xalan1Transform.java org.apache.xalan.xslt.*; ...fop.tools.xslt.XSLTransform.java Class.forName(org.apache.xalan.xslt.XSLTProcessor); I believe all this stuff could be replaced by JAXP 1.1 standard functionality. This means FOP could also be build with any JAXP 1.1 compatible XML/XSL library. This would also get rid of some unfortunate dependencies from Driver.getParserClassName() (why not use SAXParserFactory.newSAXParser().getXMLReader() instead and let the library handle all the annoying stuff? At the same time, validation could be switched off, gaining some performance in rare cases). I could try to prepare patches, however: - Is there a chance to get them into the maintenance branch? (there is a feature freeze pending, AFAIK) - Last time i tried i was not able to build FOP successfully, because of an odd ant incompatibility problem i didn't (and still don't) have time to resolve. This means i can only try basic compilation, someone else would have to finalize the patch. (Crossposted to fop-dev) Regards J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: sax conflicts with tomcat-4.0.2-LE-jdk1.4
Joerg Pietschmann wrote: [..] I believe all this stuff could be replaced by JAXP 1.1 standard functionality. This means FOP could also be build with any JAXP 1.1 compatible XML/XSL library. This would also get rid of some unfortunate dependencies from Driver.getParserClassName() (why not use SAXParserFactory.newSAXParser().getXMLReader() instead and let the library handle all the annoying stuff? At the same time, validation could be switched off, gaining some performance in rare cases). I could try to prepare patches, however: - Is there a chance to get them into the maintenance branch? (there is a feature freeze pending, AFAIK) No freezing yet .. so hurry up ;-) I've applied the patches (my commit messages don't make it to fop-cvs yet) but I want to fix a bug (#6094) and have a look at the MIF renderer which seems to be broken before doing RC2. If you send the patch untill thursday it ok. - Last time i tried i was not able to build FOP successfully, because of an odd ant incompatibility problem i didn't (and still don't) have time to resolve. This means i can only try basic compilation, someone else would have to finalize the patch. Ok, but what's your problem with ant? Regards J.Pietschmann Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]