Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] XML Parsing In an Eclipse 3.0 Plugin

Actually, there is a workaround. You can define a jarclassloader that breaks
the usual rule of depth-first class loading and loads your version of xerces
(and anything it uses) from your own jar(s). This is a PITA to get working
properly (the key is to only refer to xerces in classes loaded by the same
jarclassloader), but when it works, it works.

Bob Foster
http://xmlbuddy.com/

----- Original Message ----- 
From: "John Arthorne" <John_Arthorne@xxxxxxxxxx>
To: <eclipse-dev@xxxxxxxxxxx>
Sent: Tuesday, January 27, 2004 10:10 AM
Subject: Re: [eclipse-dev] XML Parsing In an Eclipse 3.0 Plugin


> The short answer is that some distributions of Java 1.4 have xerces
> bundled in their class libraries.  This can cause conflicts with *any*
> version of xerces that you use, and short of messing with the system class
> loader or hacking the class libraries there is no workaround.  So, the
> Eclipse SDK no longer uses the org.apache.xerces plug-in at all, and uses
> Java 1.4 JAXP APIs instead.  See:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=37696
> http://java.sun.com/xml/jaxp/reference/faqs/index.html#JDK14
> --
>
>
> eclipse-dev-admin@xxxxxxxxxxx wrote on 01/26/2004 06:41:21 PM:
>
> > Speaking of Eclipse, Xerces and plug-ins, M6 comes with an
> > "org.apache.xerces" plugin that tags itself as "version 4.0.13" (which
> > is GREATER THAN the actual latest xerces version number of 2.6.0) but on
>
> > examining its plugin.xml also declares that "This is an IBM maintenance
> > branch of xerces 2.0.0".  So, correct me if I'm wrong, but won't this
> > older version override any 2.6.0 xerces.jar that I try to import for my
> > plug-in?
> >
> > Furthermore, a grep of plugin.xml files show that none of the other
> > plugins import org.apache.xerces - presumably they do their own XML
> > thing, or use the JDK1.4 XML capabilities.
> >
> > Thus, should this plug-in be removed from the M7 distribution
> altogether?
> >
> > thanks,
> > Nigel.
> >
>



Back to the top