Richard S. Hall wrote:
Jeff McAffer wrote:
There is some work on this going on in Eclipse/Equinox. In
particular, Eclipse 3.1 has support integrating code that uses
context classloaders.
I am not sure what all of this has to do with the context class
loader...unless the idea is to find a scheme to automatically set the
context class loader so that the correct class loader gets used. I
don't see how this would work though.
What comes to mind is to wrap services obtained from a bundle with a
proxy that sets the context classloader to the bundle's classloader at
each method call of the service.
In Equinox there is some work on running multiple Equinox OSGi
frameworks in a server. This includes some investigations into the
URL handler issues. Right now this work is a bit obscure but if you
check out the mailing list archive/newsgroup you should find some
what you're looking for. See also
https://bugs.eclipse.org/bugs/show_bug.cgi?id=107909.
I have always tried to make sure that it was possible to have multiple
instances of the framework running at the same time...this is getting
more tricky now.
I am working on the URL Handlers service and it is not going to be
pretty, but I think I have a solution that will work for multiple
framework instances in a single VM. However, this solution assumes
that there are no independent 3rd parties also trying to control the
handler and content factories.
I will post some thoughts on this next week, perhaps.
Waiting for them :-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
