RE: Orion and Sax/JDom

[Trujillo, Kris]

Title: Message

The problem your having when running java -jar orion.jar to start the server is because executable jars don't use the classpath set via a CLASSPATH environment variable or via java -cp XXX -jar orion.jar.  The classpath for an executable jar is determined by what is entered in the META-INF/MANIFEST.MF for the jar file.  If you open up orion.jar you'll see that the "Class-Path" is as follows:   Class-Path: ejb.jar jndi.jar jdbc.jar jta.jar jaxp.jar crimson.jar xal  an.jar saxon.jar tools.jar jsse.jar jnet.jar jcert.jar activation.jar   mail.jar jaas.jar nls_charset12.jar The problem is that jaxp.jar and crimson.jar are both going to be placed infront of xerces.jar no matter how you configure xerces.jar into the mix.  A better fix would be to replace jaxp.jar and crimson.jar in the MANIFEST.MF with xerces.jar then update orion.jar with the new manifest file. -----Original Message----- From: Bryant Bunderson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 9:23 AM To: Orion-Interest Subject: RE: Orion and Sax/JDom I use this command to run Orion Server. It solved my Xerces and JDOM problems.   java -classpath xerces.jar;orion.jar com.evermind.server.ApplicationServer       -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Michael Laccetti Sent: Tuesday, September 04, 2001 1:10 PM To: Orion-Interest Subject: RE: Orion and Sax/JDom   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? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of The elephantwalker Sent: Tuesday, September 04, 2001 12:04 To: Orion-Interest Subject: RE: Orion and Sax/JDom 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   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Laccetti Sent: Tuesday, September 04, 2001 8:33 AM To: Orion-Interest Subject: Orion and Sax/JDom 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]