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
>
>2) add the system property to $TOMCAT_HOME/bin/tomcat.sh
> -Dorg.apache.cocoon.co
Yes Dims, that fixed it. The Xerces jar from original install of
tomcat-3.2.2 was at $TOMCAT_HOME/lib/xerces_1_4_1.jar
I replaced it with the xerces_1_4_3.jar from the Cocoon-2.1dev
dist and all is now well. How on earth could you detect that
that was the problem from the supplied error listing?
A
Nuke jaxp.jar from your tomcat/lib directory.
/LS
> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]]
> Sent: den 19 september 2001 12:10
> To: [EMAIL PROTECTED]
> Subject: startup exception when XercesParser instead of JaxpParser
>
>
> I foll
David,
Check if you have any other Xerces JAR file *ANYWHERE* in your tomcat directory
hierarchy. replace
it with the xerces in xml-cocoon2\lib directory and let us know. Also the log file
will most
likely show the location from where xerces jar was picked up so check that too.
Thanks,
dims
-
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
2) add the system property to $TOMCAT_HOME/bin/tomcat.sh
-Dorg.apache.cocoon.components.parser.Parser=
org.apache.cocoon.components.
