I have discovered a neat way to have my cake and
eat it too.
The problem: Orion is configured (via an include in
the jar file) to use crimson. Crimson doesn't support schema and adding xerces
to the lib directory makes no difference at all. I didn't want to hack the
orion.jar file as this
sure why it's having a conflict, but in general
keep in mind that classes are always loaded at the top.
Andre
-Original Message-
From: Vimal Kansal [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 03, 2001 4:48 PM
To: Orion-Interest
Subject: Re: xerces conflict (and a hack solution).
I
I also ran into this problem. I think this is a bug
with Orion. Each application deployed to Orion should
get its own unique classloader, which is distinct not
only from all other applications, it is also distinct
from the classloader that Orion uses for itself.
Vimal
--- Mark Kettner <[EMAIL PRO
:Hello all,
In our web application we use an old version of xerces. We deploy the
application with xerces.jar in the
WEB-INF/lib directory.
However, when the application is started we get the error:
java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
at
org.xml.sax.hel
