--- On Sat, 12/20/08, Brian Minchau <minc...@ca.ibm.com> wrote:
...
> The Apache Xalan-J classes have package names starting with
> org.apache.xalan or org.apache.xml or org.apache.xpath. So which objects
> are eating up memory, because your traceback doesn't show any of these.
>
> Also the exception you have occured in
> com.sun.org.apache.xpath.internal.XPathAPI, which looks like your
> problem is with SUN not Apache. Apache Xalan-J has this class:
> org.apache.xpath.XPathAPI, and that sure looks like a SUN version of
> that Apache class.
As far as I know, this is just an artifact of how most 3rd party packages are
bundled with JDK these days: Sun renames packages to make it easier to override
implementations by just plugging in "non-Sun" version of Xerces, Xalan and
other similar packages. So it should be just matter of peeling of the leading
"com.sun", and those should map to well know 'source' classes.
I think versions Sun bundled are generally quite old, due to length of release
cycle; and sometimes there are backported fixes, making it difficult to figure
exactly which version you are looking at.
Because of this, it is usually recommended that one always adds explicit Xerces
and Xalan packages and not rely on whatever default JDK comes equipped with.
This way you will be using up-to-date versions, and know exactly which versions
they are.
-+ Tatu +-
