| Xerces vs. JRE XML parsers [message #97409] |
Thu, 13 September 2007 19:08 |
Eclipse User |
|
|
|
Originally posted by: kirby.bohling.gmail.com
All,
I'm upgrading my application from using Eclipse 3.2.2 as the base, to
using Eclipse 3.3. During the Eclipse 3.2.2 phase, I had a lot of
problems with Xerces vs. the JRE XML parsers. I ran sample code in a
non-OSGi environment and everything worked. I ran it the same code in
an OSGi environment and it failed.
After a great deal of digging, I determined that that the problem was
that it was loading the JRE XML parser, instead of the Xerces parser
that I had packaged. Including the org.apache.xerces plug-in in my
application while using 3.2.2 solved my problem.
Now however, the problem appears to be back while using 3.3. It is
attempting to use the JRE XML parser, even though the xerces plug-in is
loaded and resolved/active. I know that some of the low level code
details of the handling of the System bundles and the default framework
class loader delegation (I think that's the correct term) were changed
in 3.3.
I also noticed that in the 3.2.2 version of the XML parser it included
all three of the xerces jars. In the 3.3 version it only has the one,
and depends upon another plug-in. It also includes the system.bundle
were the 3.2.2 version doesn't.
I was curious if anyone had any ideas as to what I could do. My only
guess was to add a system.bundle fragment that added org.apache.xerces
as a dependency and then have it re-export the symbols.
Thanks,
Kirby
|
|
|
Powered by
FUDForum. Page generated in 0.02453 seconds
Home