I have been using xerces with 1.3.1 albeit on WinNT
and have no problems with it. You have to make sure in
your tomcat.properties, wrapper.properties and
tomcat.bat, you mention xerces.jar on the top where
ever you configure the library files
for example in tomcat.properties
wrapper.classpath=c:\tomcat\lib\xerces.jar;
wrapper.classpath=....
the xerces.jar needs to load up in the context first
and everything should work
Goodluck
Kris
--- pete <[EMAIL PROTECTED]> wrote:
> I get this. It sucks.
>
> The issue, for me at least, stems from the fact that
> i am running a
> Struts project, and i need to override the jaxp.jar
> classes with xerces
> parser classes.
>
> I previously did this by putting a jar named
> 0xerces.jar in the lib/
> folder of my tomcat install, which worked fine,
> since those classes
> loaded before the ones specified in jaxp.jar.
>
> This worked great with IBM's JDK1.3.0 - never used
> Sun's 1.2.2 on Linux.
>
> However, since 'upgrading' to Sun's JDK1.3.1 with
> Hotspot, the JVM
> segfaults when tomcat starts up, giving the same
> error you describe.
>
> I'm not sure why this happens, but maybe 1.3.1
> doesn't like having its
> classes overridden.
>
> There are 2 ways around this - invoke the JVM with
> the '-classic'
> switch, thus disabling the JIT, or to remove
> 0xerces.jar from lib/,
> which breaks my Struts projects.
>
> The third solution is not to use the JDK1.3.1 at
> all, and stick with the
> IBM JDK, which is my current course of action.
>
> Hope this helps, and i hope you find a better
> solution than i did.
>
> -Pete
>
>
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
