[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] ClassLoader deadlock issues


Any chance you can point me at documentation about the extension registration (is that Extension points, or do you mean something at the OSGi 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 am 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, I've been working hard to ensure that they work just fine standalone in SWT applications.


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 not be
using BuddyLoading as your pluggability mechanism and should instead use
the extension registry or services.
BuddyLoading has been designed to help people integrate libraries that use
reflection and context classloaders as their extension mechanism and they
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>

To equinox-dev@xxxxxxxxxxx cc

[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 at

The ClassLoader segmentation is causing me lots and lots of issues w/
BuddyLoaders and the deadlock.

I've seen this thread:

This pretty much exactly covers my case.  Are there any workarounds or
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 issue.
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 slow
haven't bothered to test it with my real application).  Are the any fixes
work arounds?  Any guidelines I can follow to mitigate the problem.  A lot

the time my application is completely assembled at runtime via reflection.


Add fun gadgets and colorful themes to express yourself on Windows Live

_______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev

equinox-dev mailing list

Try the new Live Search today! http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG