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.SAXParserFactory" system property to "org.apache.xerces.jaxp.SAXParserFactoryImpl".
On 13.04.2006 16:49:51 John Quinn wrote: > 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: AElfred parser is > non-validating > > at com.icl.saxon.aelfred.SAXParserFactoryImpl.newSAXParser( > SAXParserFactoryImpl.java:34) > > at org.apache.commons.digester.Digester.getParser(Digester.java:686) > > at org.apache.commons.digester.Digester.getXMLReader(Digester.java:902) > > at org.apache.commons.digester.Digester.parse(Digester.java:1548) > > at org.apache.struts.action.ActionServlet.parseModuleConfigFile( > ActionServlet.java:708) > > at org.apache.struts.action.ActionServlet.initModuleConfig( > ActionServlet.java:670) > > at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329) > > at javax.servlet.GenericServlet.init(GenericServlet.java:211) > This is version6.5.3 of Saxon, as this is the version the documentation > pointed to as being compatible with FOP. But clearly not compatible with > JBoss and the application. > > Any other ideas on how to clear up the Namespace problem. <snip/> Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
