You can use Saxon's -X option to force saxon to use Xerces as the xml
parser. For command line it's something like:
java com.icl.saxon.StyleSheet -x org.apache.xerces.parsers.SAXParser
I don't know how to translate it to Cocoon instructions
Carlos
On 6/11/02 1:53 PM, "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
>
> - The DOM coming with Saxon is read-only.
>
> 0. Ant: Ant at least up to 1.4.1 uses the SAX1 interface. Hacked
> Ant to use SAX2.
>
> 1. Tomcat problems. Provided for
> - Build Tomcat from Source. Not for the faint of heart.
> - Starting Tomcat bombs in an attempt to read server.xml because
> AElfred's namespace support cannot be switched off. Deleted
> two setNamespaceAware("false") statements. A hack, but not so
> bad if seen in conjunction with the next point.
> - Starting Tomcat bombs because of SAX1 interface. Upgraded
> Catalina to SAX2 (For some odd reason, migrating to SAX2 seems
> to be a somewhat unpopular topic within parts of the Apache community)
> - Starting Tomcat still bombs with an NPE in the entity resolver
> because AElfred calls it for every input stream in order to
> allow mappings, even if the public id is not set. Reported
> as a bug and fixed by bypassing the mapping unless a public
> id is set.
> - Tomcat starts but bombs yet again while reading web.xml
> because validation is requested, and AElfred does not validate.
> Caught the ParserConfigurationException and turned off validation
> locally. Ugly workaround, but so what.
> Finally, Tomcat works.
>
> 2. Cocoon.
> - First access bombs because the default hardcoded
> DocumentBuilderFactory is not available (a crimson class). This is,
> for variety, a Saxon bug. Added
> -Djavax.xml.parsers.DocumentBuilderFactory=
> com.icl.saxon.om.DocumentBuilderFactoryImpl
> to CATALINA_OPTS to tell the JAXP implementation of Saxons DOM
> builder.
> - Next access still bombs because the sitemap cannot be compiled
> org.apache.avalon.framework.parameters.ParameterException:
> The parameter 'compiler' does not contain a value
> Added
> <parameter name="compiler"
> value="org.apache.cocoon.components.language.programming.java.Javac"/>
> to <java-language> in cocoon.xconf.
> - Next access still bombs because there is still a setting defaulting
> javax.xml.parsers.SAXParserFactory to the Xerces factory. Fixed by
> adding
> -Djavax.xml.parsers.SAXParserFactory=
> com.icl.saxon.aelfred.SAXParserFactoryImpl
> to CATALINA_OPTS.
> I have no idea where the Xerces setting came from.
> - Next access bombs yet again because org.xml.sax.driver points to
> a Xerces class. Fixed by adding
> -Dorg.xml.sax.driver=com.icl.saxon.aelfred.SAXDriver
> to CATALINA_OPTS.
--
Carlos E. Araya
---+ WebCT Administrator/Trainer
P | California Virtual Campus
- | C/O De Anza College
G | 21250 Stevens Creek Blvd
---+ Cupertino, CA 95014
email [EMAIL PROTECTED]
web http://www.cvc1.org/ (work)
http://silverwolf-net.net (personal)
phone 408 257 0420 (work)
PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
"Do not meddle in the affairs of dragons....for you are crunchy and taste
good with ketchup and mayonnaise.."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
