The extension registry == extension
/ extension points. The registry code is in the org.eclipse.equinox.registry
and it runs *outside* of OSGi.
Services == OSGi services, but from
what you say they don't seem to be an option.
<computerslicer23@xxxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/13/2006 08:35 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Re: [equinox-dev] ClassLoader deadlock
Any chance you can point me at documentation about the extension
registration (is that Extension points, or do you mean something at the
bundle level?) and services (that I'm pretty sure is an OSGi thing)? I've
poked around a bit and have found myself wanting for better documentation.
Ultimately, I do have corners I'll get stuck in, like Serialization for
remote messaging. I'll see if I can get around that.
One of the design constraints, is that I can't be tied to Eclipse. I
part of the tools team at my work, and the tools have to work both inside
and outside of Eclipse. So while aspects of it support Eclipse well,
been working hard to ensure that they work just fine standalone in SWT
>From: Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
>Reply-To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>CC: equinox-dev@xxxxxxxxxxx, equinox-dev-bounces@xxxxxxxxxxx
>Subject: Re: [equinox-dev] ClassLoader deadlock issues
>Date: Fri, 13 Oct 2006 19:58:39 -0400
>If you are the author of the main and children plug-ins, you should
>using BuddyLoading as your pluggability mechanism and should instead
>the extension registry or services.
>BuddyLoading has been designed to help people integrate libraries that
>reflection and context classloaders as their extension mechanism and
>can't change the code.
>"Kirby Bohling" <computerslicer23@xxxxxxxxxxx>
>Sent by: equinox-dev-bounces@xxxxxxxxxxx
>10/13/2006 05:10 PM
>Please respond to
>Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>[equinox-dev] ClassLoader deadlock issues
>I've been working with Eclipse, and use Buddy Loaders fairly extensively
>that core plug-ins can construct objects from their child plug-ins
>The ClassLoader segmentation is causing me lots and lots of issues
>BuddyLoaders and the deadlock.
>I've seen this thread:
>This pretty much exactly covers my case. Are there any workarounds
>mitigations? I use object serialization for over the wire communication
>spring both of which use Global buddy loaders. Currently my application
>deadlocks 9 times out of 10.
>I've been looking into writing my own classloader to deal with the
>That hasn't gotten me very far (I've inserted my own classloader that
>all class loads to happen on a single threading context, but it's so
>haven't bothered to test it with my real application). Are the
>work arounds? Any guidelines I can follow to mitigate the problem.
>the time my application is completely assembled at runtime via reflection.
>Add fun gadgets and colorful themes to express yourself on Windows
>equinox-dev mailing list
>equinox-dev mailing list
Try the new Live Search today!
equinox-dev mailing list