cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject Re: startup exception when XercesParser instead of JaxpParser
Date Thu, 20 Sep 2001 09:15:17 GMT
At 8:09 PM +1000 19/9/01, David Crossley wrote:
>I followed the instructions in 2.1-dev webapp/cocoon.xconf
>to activate the XercesParser instead of the default JaxpParser ...
>1) add parser entry to cocoon.xconf
> <parser class="... parser.XercesParser"/>
>2) add the system property to $TOMCAT_HOME/bin/
> -Dorg.apache.cocoon.components.parser.Parser=
> org.apache.cocoon.components.parser.XercesParser

This does not solve your problem, but when need to add extra command line
stuff to TomCat's "launch string", instead of editing (and keeping your
changes in), you might find it more convenient to set up an
environment variable called $TOMCAT_OPTS, it's contents are automatically
added to the command line by

Hope this helps

regards Jeremy

   Jeremy Quinn                                           Karma Divers
                                                       webSpace Design
                                            HyperMedia Research Centre

   <>     		 <>
   <phone:+44.[0].20.7737.6831>             <>

To unsubscribe, e-mail:
For additional commands, email:

View raw message