Re: JDOM and orion 1.5.2
Hello guys
Has anyone of you got JDOM to work with orion 1.5.2 ???
I have jdom6 in {ORIONDIR}/lib and lastest version of xerces.jar in
{ORIONDIR}/
still got the problem like below
org.jdom.JDOMException: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:231)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Root cause: java.lang.ClassNotFoundException:
org.apache.xerces.parsers.SAXParser
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1
18)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:167)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Can anybody give me some hint ?
thanks
-alexander
Tommy Eriksson wrote:
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
/Tommy
RE: JDOM and orion 1.5.2
I finally got it to work. The thing was to erased the xerces file. JDOM beta
6 can use JAXP to find the crimson XML parser and use that one.
1. Delete xerces
2. Create a JDOM SAX builder:
SAXBuilder builder = new SAXBuilder(false);
Hope it helps.
/Tommy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: den 28 juni 2001 23:51
To: Orion-Interest
Subject: Re: JDOM and orion 1.5.2
Hello guys
Has anyone of you got JDOM to work with orion 1.5.2 ???
I have jdom6 in {ORIONDIR}/lib and lastest version of xerces.jar in
{ORIONDIR}/
still got the problem like below
org.jdom.JDOMException: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:231)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Root cause: java.lang.ClassNotFoundException:
org.apache.xerces.parsers.SAXParser
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1
18)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:167)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Can anybody give me some hint ?
thanks
-alexander
Tommy Eriksson wrote:
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to
1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces
to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
/Tommy
RE: JDOM and orion 1.5.2
Title: RE: JDOM and orion 1.5.2
This
was the way to go, I had to rewrite some of my code but now everything works
fine. Thanks
/Tommy
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Kesav
KumarSent: den 7 juni 2001 18:33To:
Orion-InterestSubject: RE: JDOM and orion
1.5.2
I think you might be using old version of JDOM. Update
your JDOM with latest beta6 or what ever. Now JDOM is also a JAXP
complince. JDOM uses JAXP for searching parsers.
Kesav Kumar Software Engineer
Voquette, Inc. 650 356 3740
mailto:[EMAIL PROTECTED]
http://www.voquette.com Voquette...Delivering Sound Information
-Original Message- From: Tommy
Eriksson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 12:29 AM To: Orion-Interest Subject: JDOM and orion
1.5.2
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and
it works fine (except that it sometimes hangs for a
while). When I updated orion to 1.5.2 I got the a
problem with JDOM complaining about SAX Parser not found. I think this is because JDOM uses xerces and orion have changed from
xerces to crimson. I have tride moving xerces.jar to
{jre}\lib\ext, but then orion won't even start. So I
think that orion reqiuires crimson to be the first XML
Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with
orion 1.5.2?
The exception I get when trying to use JDOM: -- org.jdom.JDOMException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at
org.jdom.input.SAXBuilder.build(SAXBuilder.java:231)
at
org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at
knut.protocol.KSPParser.parse(KSPParser.java:46) ... Root cause:
java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1
18)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:167)
at
org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at
knut.protocol.KSPParser.parse(KSPParser.java:46) ...
/Tommy
JDOM and orion 1.5.2
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
The exception I get when trying to use JDOM:
--
org.jdom.JDOMException: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:231)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Root cause: java.lang.ClassNotFoundException:
org.apache.xerces.parsers.SAXParser
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1
18)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:167)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
/Tommy
Re: JDOM and orion 1.5.2
Tommy Eriksson wrote:
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
/Tommy
We're having the same problem. I've tried to put xerces.jar in the
classpath declaration of orion.jar's MANIFEST.MF, but it continues
failing.
Can JDOM beta 6 work with crimson instead of xerces?
Thanks
--
··
Juan Fuentes Nieto Essi Projects
[EMAIL PROTECTED]t +34 977 221 182
http://www.essiprojects.com f +34 977 230 170
··
Re: JDOM and orion 1.5.2
does it work If you start the orionserver with ...
java -classpath sax2.jar;xerces.jar;jaxp.jar;jdom.jar;orion.jar;lib/xmlrpc.jar
com.evermind.server.ApplicationServer
( I've downloaded sax2.jar and jdom.jar somewhere ... you have to put sax2.jar and
jdom.jar in the same directory as orion.jar . )
*** REPLY SEPARATOR ***
On 7-6-01 at 12:04 Juan Fuentes wrote:
Tommy Eriksson wrote:
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
/Tommy
We're having the same problem. I've tried to put xerces.jar in the
classpath declaration of orion.jar's MANIFEST.MF, but it continues
failing.
Can JDOM beta 6 work with crimson instead of xerces?
Thanks
--
··
Juan Fuentes Nieto Essi Projects
[EMAIL PROTECTED]t +34 977 221 182
http://www.essiprojects.com f +34 977 230 170
··
RE: JDOM and orion 1.5.2
Title: RE: JDOM and orion 1.5.2
I think you might be using old version of JDOM. Update your JDOM with latest beta6 or what ever. Now JDOM is also a JAXP complince. JDOM uses JAXP for searching parsers.
Kesav Kumar
Software Engineer
Voquette, Inc.
650 356 3740
mailto:[EMAIL PROTECTED]
http://www.voquette.com
Voquette...Delivering Sound Information
-Original Message-
From: Tommy Eriksson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 12:29 AM
To: Orion-Interest
Subject: JDOM and orion 1.5.2
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
The exception I get when trying to use JDOM:
--
org.jdom.JDOMException: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:231)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
Root cause: java.lang.ClassNotFoundException:
org.apache.xerces.parsers.SAXParser
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1
18)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:167)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:323)
at knut.protocol.KSPParser.parse(KSPParser.java:46)
...
/Tommy
SV: JDOM and orion 1.5.2
Title: SV: JDOM and orion 1.5.2
Maybee setting the java.sax.driver system property (or whatever it is called I don't remember) like:
java -Djava.sax.driver=com.acme.sax.SAX2 -jar orion.jar ?
-Ursprungligt meddelande-
Från: Steven De Schutter [mailto:[EMAIL PROTECTED]]
Skickat: den 7 juni 2001 17:58
Till: Orion-Interest
Ämne: Re: JDOM and orion 1.5.2
does it work If you start the orionserver with ...
java -classpath sax2.jar;xerces.jar;jaxp.jar;jdom.jar;orion.jar;lib/xmlrpc.jar com.evermind.server.ApplicationServer
( I've downloaded sax2.jar and jdom.jar somewhere ... you have to put sax2.jar and jdom.jar in the same directory as orion.jar . )
*** REPLY SEPARATOR ***
On 7-6-01 at 12:04 Juan Fuentes wrote:
Tommy Eriksson wrote:
Hi,
I have a problem that is driving me crazy.
I have been using orion 1.3.8 and jdom for some time now and it works fine
(except that it sometimes hangs for a while). When I updated orion to 1.5.2
I got the a problem with JDOM complaining about SAX Parser not found. I
think this is because JDOM uses xerces and orion have changed from xerces to
crimson. I have tride moving xerces.jar to {jre}\lib\ext, but then orion
won't even start. So I think that orion reqiuires crimson to be the first
XML Parser in the class path and JDOM requires xerces to be the first XML
Parser in the class path.
So my questions are:
1) Has anyone got JDOM to work with orion 1.5.2?
2) Does anyone have any Idea on how to get JDOM to work with orion 1.5.2?
/Tommy
We're having the same problem. I've tried to put xerces.jar in the
classpath declaration of orion.jar's MANIFEST.MF, but it continues
failing.
Can JDOM beta 6 work with crimson instead of xerces?
Thanks
--
··
Juan Fuentes Nieto Essi Projects
[EMAIL PROTECTED] t +34 977 221 182
http://www.essiprojects.com f +34 977 230 170
··
Re: JDom and Orion
Well, David Kinnvall, did you ever get into any trouble from replacing the versions of Xerces and Xalan in Orion? Randahl Hi Mark, and the list, I ran into this as well, just two days ago. I tried putting the new xerces.jar in WEB-INF/lib as well as in orion/lib, with no effect. Finally I simply replaced the $ORION_DIR/xerces.jar with the new one as you are thinking about. It worked nicely, and I have not seen any ill effects from it yet. JDOM is very nice! I guess your question is still valid though: Are there any bad effects from doing this that will surface along the road that I haven't seen yet? Something that is not triggered by my current code? Or is Orion compatible with newer versions of Xerces? Oh, almost forgot, I took the opportunity to replace the old Xalan with the latest one as well... Regards, David.
Re: JDom and Orion
Actually, no. No problem at all! /David On Sun, 11 Mar 2001, Randahl Fink Isaksen wrote: Well, David Kinnvall, did you ever get into any trouble from replacing the versions of Xerces and Xalan in Orion? Randahl -- David, [EMAIL PROTECTED]
Re: JDom and Orion
Hi Mark, and the list, I ran into this as well, just two days ago. I tried putting the new xerces.jar in WEB-INF/lib as well as in orion/lib, with no effect. Finally I simply replaced the $ORION_DIR/xerces.jar with the new one as you are thinking about. It worked nicely, and I have not seen any ill effects from it yet. JDOM is very nice! I guess your question is still valid though: Are there any bad effects from doing this that will surface along the road that I haven't seen yet? Something that is not triggered by my current code? Or is Orion compatible with newer versions of Xerces? Oh, almost forgot, I took the opportunity to replace the old Xalan with the latest one as well... Regards, David. On Fri, 15 Dec 2000 [EMAIL PROTECTED] wrote: Hi all, I am trying to use the most excellent JDom in my web app on Orion (1.3.9) and running into a little snag. For certain parts of its funcationality, JDom requires a very recent version of Xerces. The datestamp on it is Sep 1, 2000 and it is approx 1,464KBs. As you can tell this is almost three times as big as the xerces jar that is shiped with Orion. I have tried to include the new xerces.jar in the /WEB-INF/lib directory of my war file but to no avail. Orion seems content to pick up its version of the jar (I imagine its a classloader thing). So my question is, is it ok to swap out Orion's old xerces.jar for the new one? Will I run into unforseen trouble down the road? Is there another way of solving this problem that i am unaware of or too ignorant to figure out? thanks a bunch... mark Mark R Mascolino The Procter Gamble Co. [EMAIL PROTECTED] Reach me by - Email: [EMAIL PROTECTED], WWW: http://www.dtek.chalmers.se/~d0dak/ - --/David---
Re: JDom and Orion
On Fri, 15 Dec 2000 [EMAIL PROTECTED] wrote: So my question is, is it ok to swap out Orion's old xerces.jar for the new one? Will I run into unforseen trouble down the road? Is there another way of solving this problem that i am unaware of or too ignorant to figure out? Xerces has had a consistent interface for many versions back, and installing the latest release (Xerces-J v1.2.3) hasn't given me any problems. I wouldn't recommend installing the development-track "Xerces 2" which is alpha quality and may not implement the same interface. - J -[ Joshua Goodall ]--- -[ Chief Systems Architect, IP RD ]- Cook, Geek, Lover -- -[ [EMAIL PROTECTED] ]--- [EMAIL PROTECTED] --
JDom and Orion
Hi all, I am trying to use the most excellent JDom in my web app on Orion (1.3.9) and running into a little snag. For certain parts of its funcationality, JDom requires a very recent version of Xerces. The datestamp on it is Sep 1, 2000 and it is approx 1,464KBs. As you can tell this is almost three times as big as the xerces jar that is shiped with Orion. I have tried to include the new xerces.jar in the /WEB-INF/lib directory of my war file but to no avail. Orion seems content to pick up its version of the jar (I imagine its a classloader thing). So my question is, is it ok to swap out Orion's old xerces.jar for the new one? Will I run into unforseen trouble down the road? Is there another way of solving this problem that i am unaware of or too ignorant to figure out? thanks a bunch... mark Mark R Mascolino The Procter Gamble Co. [EMAIL PROTECTED]
Re: JDom and Orion
I have swapped out the Orion xerces JAR in favor of a newer version, and I have not seen any problems associated with that change. tim. Hi all, I am trying to use the most excellent JDom in my web app on Orion (1.3.9) and running into a little snag. For certain parts of its funcationality, JDom requires a very recent version of Xerces. The datestamp on it is Sep 1, 2000 and it is approx 1,464KBs. As you can tell this is almost three times as big as the xerces jar that is shiped with Orion. I have tried to include the new xerces.jar in the /WEB-INF/lib directory of my war file but to no avail. Orion seems content to pick up its version of the jar (I imagine its a classloader thing). So my question is, is it ok to swap out Orion's old xerces.jar for the new one? Will I run into unforseen trouble down the road? Is there another way of solving this problem that i am unaware of or too ignorant to figure out? thanks a bunch... mark Mark R Mascolino The Procter Gamble Co. [EMAIL PROTECTED]
