Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Orbit » javax.xml buddy policy
javax.xml buddy policy [message #547410] Fri, 16 July 2010 16:40 Go to next message
Remko Tronçon is currently offline Remko Tronçon
Messages: 4
Registered: July 2010
Junior Member
Hi,

I'm using the Eclipse java.xml bundle to do XML parsing. I want to register my own SAX driver, which I do by setting the "org.xml.sax.driver" property. However, when I try to create a parser, I get an exception that the classname I passed as the property is not found.

My assumption is that this is because the class comes from one of my plugins, and therefore the java.xml plugin can't see it. Could this be fixed by having a BuddyPolicy in java.xml? Is this something that the Orbit project would do, or should I create my own fork of the java.xml plugin?

thanks!
Remko
Re: javax.xml buddy policy [message #548111 is a reply to message #547410] Tue, 20 July 2010 16:40 Go to previous message
David Williams is currently offline David Williams
Messages: 176
Registered: July 2009
Senior Member
remko@el-tramo.be wrote:
> Hi,
>
> I'm using the Eclipse java.xml bundle to do XML parsing. I want to
> register my own SAX driver, which I do by setting the
> "org.xml.sax.driver" property. However, when I try to create a parser, I
> get an exception that the classname I passed as the property is not found.
>
> My assumption is that this is because the class comes from one of my
> plugins, and therefore the java.xml plugin can't see it. Could this be
> fixed by having a BuddyPolicy in java.xml? Is this something that the
> Orbit project would do, or should I create my own fork of the java.xml
> plugin?
>
> thanks!
> Remko

I've not heard of this issue before. And do know we used to have to
change the sax parser, but then it was due to some vm difference.
Not too sure too many people have tried, just to provide their own.
I'd suggest opening a bug in Orbit where it could be discussed in more
detail. It'd help if a test case was provided (even if a simply
"example" test case). The answer on whether buddy-class loading is the
right solution probably depends on exactly how the javax.xml
implementation creates a 'new instance' which I'd have to investigate.
Re: javax.xml buddy policy [message #565918 is a reply to message #547410] Tue, 20 July 2010 16:40 Go to previous message
David Williams is currently offline David Williams
Messages: 176
Registered: July 2009
Senior Member
remko@el-tramo.be wrote:
> Hi,
>
> I'm using the Eclipse java.xml bundle to do XML parsing. I want to
> register my own SAX driver, which I do by setting the
> "org.xml.sax.driver" property. However, when I try to create a parser, I
> get an exception that the classname I passed as the property is not found.
>
> My assumption is that this is because the class comes from one of my
> plugins, and therefore the java.xml plugin can't see it. Could this be
> fixed by having a BuddyPolicy in java.xml? Is this something that the
> Orbit project would do, or should I create my own fork of the java.xml
> plugin?
>
> thanks!
> Remko

I've not heard of this issue before. And do know we used to have to
change the sax parser, but then it was due to some vm difference.
Not too sure too many people have tried, just to provide their own.
I'd suggest opening a bug in Orbit where it could be discussed in more
detail. It'd help if a test case was provided (even if a simply
"example" test case). The answer on whether buddy-class loading is the
right solution probably depends on exactly how the javax.xml
implementation creates a 'new instance' which I'd have to investigate.
Previous Topic:GWT-User not installable with p2
Next Topic:SLF4j Version 1.6.0
Goto Forum:
  


Current Time: Thu Oct 02 02:28:10 GMT 2014

Powered by FUDForum. Page generated in 0.02118 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software