Greetings.
I was having some similiar issues with classes from Xerces/Xalan. We
found an effective workaround was by copying/linking the xerces.jar and
xalan.jar files into the lib directory under Orion.
I am thinking that this may be part of the same issue where utility jars
in ear files are not being read. This is something I currently have an
open support call with Orion for. (Workaround was the same, copy the
utility jars to the lib directory...)
-Steve
Title: Message
I
did a fresh install, downloaded the latest zip and installed it. I've
tried downloading the latest version of xerces and replacing the version with
1.5.2 with that. Again, still getting the SAX2 not found exception.
Is there a specific order to set in the classpath?
Michael,
We
use jdom b7 and orion 1.5.2 all of the time....with no problems. We use
jdom with crimson, which is the default parser with jdom and orion version
1.5.2. Orion 1.4.6 used an old version of xerces. Did you use
autoupdate.jar to install 1.5.2 or did you use a fresh install? Autoupdate.jar
is a little unreliable, so I would do a fresh install.
regards,
the
elephantwalker
I've recently installed Orion 1.5.2 on a linux test machine, and
installed our app on it. It worked fine under 1.4.6, but for some
reason, when I dump it under 1.5.2 I keep getting a SAX2 exception:
SAX2 driver class not found. Has anybody seen this before, and better
yet, fixed it? I've tried everything that I can think of. I even
grabbed the latest version of JDom and installed that. Please
help!
-------------------------------------
Michael Laccetti
Developer, Eldan
Software
[EMAIL PROTECTED]
