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.
> >
> >
> >
> >