Xerces.jar
After upgrading to orion 1.5.1, orion would not find xerces.jar anymore in the classpath. I placed it in orion/lib - nothing I placed it in the application lib - nothing I placed it in the WEB-INF/lib - nothing Then I decided to the check the orion.jar manifest, and noticed that xerces.jar was not in the classpath anymore. I then updated the manifest so that xerces.jar is in the classpath and now it finds the package. I don't want this to be part of the deployment process. Is there an easier way to make orion realize that xerces.jar should be in the classpath? Shoud I not be using xerces.jar? The file that orion complains about is: java.lang.NoClassDefFoundError: org/apache/xalan/xslt/XSLTProcessorFactory
RE: Xerces.jar
java.lang.NoClassDefFoundError: org/apache/xalan/xslt/XSLTProcessorFactory This file is in Xalan.jar not Xerces.jar ? Orion no longer needs Xerces, it uses JAXP and Crimson instead. You should code to the JAXP API anyway, not to Xerces specific APIs - for portability. -mike
Re: Xerces.jar
If you want your xerces.jar to be picked from your classpath keep xerces.jar in jre\lib\ext directory. - Original Message - From: Eduardo Estefano [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, June 05, 2001 8:46 AM Subject: Xerces.jar After upgrading to orion 1.5.1, orion would not find xerces.jar anymore in the classpath. I placed it in orion/lib - nothing I placed it in the application lib - nothing I placed it in the WEB-INF/lib - nothing Then I decided to the check the orion.jar manifest, and noticed that xerces.jar was not in the classpath anymore. I then updated the manifest so that xerces.jar is in the classpath and now it finds the package. I don't want this to be part of the deployment process. Is there an easier way to make orion realize that xerces.jar should be in the classpath? Shoud I not be using xerces.jar? The file that orion complains about is: java.lang.NoClassDefFoundError: org/apache/xalan/xslt/XSLTProcessorFactory
Re: How about the latest xerces.jar and xalan.jar? - memory leak
Per xml.apache.org you'll need to update xalan along with xerces - the xalan download includes both of them. We're using 1.2.D02 with no problems, but haven't tried 2.0 yet. Kirk Yarina At 09:33 AM 3/14/01 +1000, you wrote: Dear all, Just a warning to anyone using xerces in their web app. The current version of xerces shipped with orion sort of leaks memory (xerces issue, not orions). org.w3c.Document objects continue to hold a reference to any org.w3c.traversal.TreeWalker objects created so if the TreeWalker goes out of scope it's not garbage collected. The latest release of Xerces, Document doesn't hold a reference to TreeWalker. In a scenario where: 1. your web app through a servlet or jsp loads a xml config file as a static variable 2. on subsequent posts or gets creates a TreeWalker to go over the Document you will be *leaking memory* unless you manually call removeTreeWalker in a xerces specific way. If orion shipped the latest xerces/xalan then this problem would go away and we'd have access to better transformation libraries, etc. We've tried replacing xerces.jar with the latest version. It fixes the memory leak problem but xalan falls over Greg. - Original Message - From: "Ted R. Rice" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Saturday, March 10, 2001 4:58 AM Subject: RE: How about the latest xerces.jar and xalan.jar? i've experience similar issues with orion 1.4.7 and saxon 6.2.1. if you update the versions of xerces to 1.3 and xalan to 2.0, you will get the MethodNotFound error when doing any javax.xml package calls. only way i got around it was: 1. remove jaxp.jar from the orion dir 2. open up xalan.jar and remove all the javax.xml classes additionally, we use UTF-8 encoding on all of XML/XSLT files to support localization. if you set the default-charset in the global-web-applicaiton.xml to be UTF-8 it will not work as it complains about unrecognized UTF-8 characters in the XML files. hoewever, the second you remove the default-charset it works perfectly. everything i've mentioned was never a problem until 1.4.7. none of our code has changed and it never had an issue with the default-charset, jaxp, or xalan/xerces. ted rice -Original Message- From: Duffey, Kevin Sent: Fri 3/9/2001 9:42 AM To: Orion-Interest Cc: Subject: How about the latest xerces.jar and xalan.jar? Orion team (and whoever else is interested), I am working on a small framework that uses Saxon and requires the latest xerces.jar file. I just did an autoupdate and it downloaded xerces.jar into the orion folder (I deleted the one that was there because of the problem I am about to describe). When I started my app, the MethodNotFound error I got when I left the 589KB version of xerces.jar in the Orion folder came back. So two things. First, can you please add the latest xerces 1.3.0. Its 1.5MB in size, but it adds a lot of new functionality that some of us are now using. Secondly, why is it when xerces.jar is in the Orion folder, Orion does NOT use the version I have in the WEB-INF/lib folder? I thought (sorry if I don't recall what the specs say on this) that libraries in the WEB-INF/lib of a web-app override the ones in a server dir? Thanks.
Re: How about the latest xerces.jar and xalan.jar? - memory leak
Dear all, Just a warning to anyone using xerces in their web app. The current version of xerces shipped with orion sort of leaks memory (xerces issue, not orions). org.w3c.Document objects continue to hold a reference to any org.w3c.traversal.TreeWalker objects created so if the TreeWalker goes out of scope it's not garbage collected. The latest release of Xerces, Document doesn't hold a reference to TreeWalker. In a scenario where: 1. your web app through a servlet or jsp loads a xml config file as a static variable 2. on subsequent posts or gets creates a TreeWalker to go over the Document you will be *leaking memory* unless you manually call removeTreeWalker in a xerces specific way. If orion shipped the latest xerces/xalan then this problem would go away and we'd have access to better transformation libraries, etc. We've tried replacing xerces.jar with the latest version. It fixes the memory leak problem but xalan falls over Greg. - Original Message - From: "Ted R. Rice" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Saturday, March 10, 2001 4:58 AM Subject: RE: How about the latest xerces.jar and xalan.jar? i've experience similar issues with orion 1.4.7 and saxon 6.2.1. if you update the versions of xerces to 1.3 and xalan to 2.0, you will get the MethodNotFound error when doing any javax.xml package calls. only way i got around it was: 1. remove jaxp.jar from the orion dir 2. open up xalan.jar and remove all the javax.xml classes additionally, we use UTF-8 encoding on all of XML/XSLT files to support localization. if you set the default-charset in the global-web-applicaiton.xml to be UTF-8 it will not work as it complains about unrecognized UTF-8 characters in the XML files. hoewever, the second you remove the default-charset it works perfectly. everything i've mentioned was never a problem until 1.4.7. none of our code has changed and it never had an issue with the default-charset, jaxp, or xalan/xerces. ted rice -Original Message- From: Duffey, Kevin Sent: Fri 3/9/2001 9:42 AM To: Orion-Interest Cc: Subject: How about the latest xerces.jar and xalan.jar? Orion team (and whoever else is interested), I am working on a small framework that uses Saxon and requires the latest xerces.jar file. I just did an autoupdate and it downloaded xerces.jar into the orion folder (I deleted the one that was there because of the problem I am about to describe). When I started my app, the MethodNotFound error I got when I left the 589KB version of xerces.jar in the Orion folder came back. So two things. First, can you please add the latest xerces 1.3.0. Its 1.5MB in size, but it adds a lot of new functionality that some of us are now using. Secondly, why is it when xerces.jar is in the Orion folder, Orion does NOT use the version I have in the WEB-INF/lib folder? I thought (sorry if I don't recall what the specs say on this) that libraries in the WEB-INF/lib of a web-app override the ones in a server dir? Thanks.
How about the latest xerces.jar and xalan.jar?
Orion team (and whoever else is interested), I am working on a small framework that uses Saxon and requires the latest xerces.jar file. I just did an autoupdate and it downloaded xerces.jar into the orion folder (I deleted the one that was there because of the problem I am about to describe). When I started my app, the MethodNotFound error I got when I left the 589KB version of xerces.jar in the Orion folder came back. So two things. First, can you please add the latest xerces 1.3.0. Its 1.5MB in size, but it adds a lot of new functionality that some of us are now using. Secondly, why is it when xerces.jar is in the Orion folder, Orion does NOT use the version I have in the WEB-INF/lib folder? I thought (sorry if I don't recall what the specs say on this) that libraries in the WEB-INF/lib of a web-app override the ones in a server dir? Thanks.
RE: How about the latest xerces.jar and xalan.jar?
i've experience similar issues with orion 1.4.7 and saxon 6.2.1. if you update the versions of xerces to 1.3 and xalan to 2.0, you will get the MethodNotFound error when doing any javax.xml package calls. only way i got around it was: 1. remove jaxp.jar from the orion dir 2. open up xalan.jar and remove all the javax.xml classes additionally, we use UTF-8 encoding on all of XML/XSLT files to support localization. if you set the default-charset in the global-web-applicaiton.xml to be UTF-8 it will not work as it complains about unrecognized UTF-8 characters in the XML files. hoewever, the second you remove the default-charset it works perfectly. everything i've mentioned was never a problem until 1.4.7. none of our code has changed and it never had an issue with the default-charset, jaxp, or xalan/xerces. ted rice -Original Message- From: Duffey, Kevin Sent: Fri 3/9/2001 9:42 AM To: Orion-Interest Cc: Subject: How about the latest xerces.jar and xalan.jar? Orion team (and whoever else is interested), I am working on a small framework that uses Saxon and requires the latest xerces.jar file. I just did an autoupdate and it downloaded xerces.jar into the orion folder (I deleted the one that was there because of the problem I am about to describe). When I started my app, the MethodNotFound error I got when I left the 589KB version of xerces.jar in the Orion folder came back. So two things. First, can you please add the latest xerces 1.3.0. Its 1.5MB in size, but it adds a lot of new functionality that some of us are now using. Secondly, why is it when xerces.jar is in the Orion folder, Orion does NOT use the version I have in the WEB-INF/lib folder? I thought (sorry if I don't recall what the specs say on this) that libraries in the WEB-INF/lib of a web-app override the ones in a server dir? Thanks. winmail.dat
Re: How about the latest xerces.jar and xalan.jar?
Hello Kevin, Friday, March 09, 2001, 1:42:59 PM, you wrote: DK Secondly, why is it when xerces.jar is in the Orion folder, Orion DK does NOT use the version I have in the WEB-INF/lib folder? I thought (sorry DK if I don't recall what the specs say on this) that libraries in the DK WEB-INF/lib of a web-app override the ones in a server dir? Yes.. and no. The problem is that orion ADD /lib and WEB-INF/lib to the classpath, but if you look at the manifest file in orion.jar you can see that xerces.jar in the root dir is declared to be in the classpath at the beginning of orion execution, so if you refer to classes in xerces.jar it will use the ones in the root dir because they are the first found. -- Best regards, Rafaelmailto:[EMAIL PROTECTED]
Re: Is xerces.jar too old ?
Yes it is. Get the latest and put it in orion/ and it will work fine. I also use jdom and it works fine. It will not cause side affects since the only difference is the DOM level supported. Matt Boris Erukhimov wrote: Our application uses XML data exchange wrapped into HTTP. It is handled by a servlet running under Orion and doing its own XML parsing and generating. We are using pretty convenient XML API (Jdom ) from http://www.jdom.org which I highly recommend. The jdom.jar bundle comes with the latest (?) xerces.jar which I also copied into /Orion/lib directory. My standalone code worked fine, but after I placed it into servlet it did throw NoSuchMethodException complaining at some xerces code. Apparently Orion's classloader uses xerces.jar from the Orion root directory prior to the one placed in Orion/lib directory. Everything works fine after I replaced the old xerces.jar in the Orion root directory with the new one which came with jdom.jar bundle. I don't like that hack because it's an alteration to Orion distribution and hell knows what side effects it may cause. So, my question are : Is there any way to force servlet in using certain library if there is some naming conflict with the one in Orion root ? Orion team, are you going to update xerces.jar in distribution ? Does it involve any licensing issue ? Thanks ~boris
Re: Is xerces.jar too old ?
Has anyone tried Xalan Java 2.0.0 yet? If so, how well did it work? Kirk Yarina At 08:23 AM 2/20/01 -0600, you wrote: Yes it is. Get the latest and put it in orion/ and it will work fine. I also use jdom and it works fine. It will not cause side affects since the only difference is the DOM level supported. Matt Boris Erukhimov wrote: ... Everything works fine after I replaced the old xerces.jar in the Orion root directory with the new one which came with jdom.jar bundle. I don't like that hack because it's an alteration to Orion distribution and hell knows what side effects it may cause.
RE: Is xerces.jar too old ?
I have, and it rocks. Much easier interfaces. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of KirkYarina Sent: Tuesday, February 20, 2001 11:28 AM To: Orion-Interest Subject: Re: Is xerces.jar too old ? Has anyone tried Xalan Java 2.0.0 yet? If so, how well did it work? Kirk Yarina At 08:23 AM 2/20/01 -0600, you wrote: Yes it is. Get the latest and put it in orion/ and it will work fine. I also use jdom and it works fine. It will not cause side affects since the only difference is the DOM level supported. Matt Boris Erukhimov wrote: ... Everything works fine after I replaced the old xerces.jar in the Orion root directory with the new one which came with jdom.jar bundle. I don't like that hack because it's an alteration to Orion distribution and hell knows what side effects it may cause.
Is xerces.jar too old ?
Our application uses XML data exchange wrapped into HTTP. It is handled by a servlet running under Orion and doing its own XML parsing and generating. We are using pretty convenient XML API (Jdom ) from http://www.jdom.org which I highly recommend. The jdom.jar bundle comes with the latest (?) xerces.jar which I also copied into /Orion/lib directory. My standalone code worked fine, but after I placed it into servlet it did throw NoSuchMethodException complaining at some xerces code. Apparently Orion's classloader uses xerces.jar from the Orion root directory prior to the one placed in Orion/lib directory. Everything works fine after I replaced the old xerces.jar in the Orion root directory with the new one which came with jdom.jar bundle. I don't like that hack because it's an alteration to Orion distribution and hell knows what side effects it may cause. So, my question are : Is there any way to force servlet in using certain library if there is some naming conflict with the one in Orion root ? Orion team, are you going to update xerces.jar in distribution ? Does it involve any licensing issue ? Thanks ~boris
RE: Is xerces.jar too old ?
Hi, We just had the same problems. The $ORION_HOME/xerces.jar version is old and could not handle our need in XML parsing. We have replaced this file by a new version and all is fine! We use Orion 1.4.4, old xerces.jar was 589 KO, and new one is 769 KO (don't know how to check version...). I know this is not a good solution, but Orion seems to give his own CLASSPATH to the application he ran, so even if you had the new xerces.jar in the CLASSPATH specified with LIB tag it'll be hidden by the Orion's one. If some have idears on this subject... PHiL -Message d'origine- De : Boris Erukhimov [mailto:[EMAIL PROTECTED]] Envoy : lundi 19 fvrier 2001 17:50 : Orion-Interest Objet : Is xerces.jar too old ? Our application uses XML data exchange wrapped into HTTP. It is handled by a servlet running under Orion and doing its own XML parsing and generating. We are using pretty convenient XML API (Jdom ) from http://www.jdom.org which I highly recommend. The jdom.jar bundle comes with the latest (?) xerces.jar which I also copied into /Orion/lib directory. My standalone code worked fine, but after I placed it into servlet it did throw NoSuchMethodException complaining at some xerces code. Apparently Orion's classloader uses xerces.jar from the Orion root directory prior to the one placed in Orion/lib directory. Everything works fine after I replaced the old xerces.jar in the Orion root directory with the new one which came with jdom.jar bundle. I don't like that hack because it's an alteration to Orion distribution and hell knows what side effects it may cause. So, my question are : Is there any way to force servlet in using certain library if there is some naming conflict with the one in Orion root ? Orion team, are you going to update xerces.jar in distribution ? Does it involve any licensing issue ? Thanks ~boris
