Eclipse Community Forums: Equinox » EclipseClassLoader vs xmlBlaster

Home » Eclipse Projects » Equinox » EclipseClassLoader vs xmlBlaster

EclipseClassLoader vs xmlBlaster [message #58878]

Mon, 30 January 2006 08:58

Eclipse User

Originally posted by: yavin.gmx.com

Hey uses someone a xmlBlaster Client as OSGi bundle?

My problem is that xmlBlaster creates its own class loader and tries to
get the classpaths form the classloader which loaded the factory. I'm
afraid they expect a URLClassloader but its the EclipseClassloader and I
get a ClassCastException.

Tips and tricks are welcome!

Re: EclipseClassLoader vs xmlBlaster [message #59003 is a reply to message #58878]

Tue, 31 January 2006 09:43

Eclipse User

Originally posted by: jeff_nospam_mcaffer.ca.ibm.com

No knowledge of xmlBlaster but we have seen similar situations. For
example, the Ant code needs to get a classpath for the Ant classloader.
Depending on the actual shape you want, you can construct a classloader
wrapper (extends Classloader) that answers all the right questions by
forwarding to the relevant methods on Bundle (Bundle.loadClass, ...).

Jeff

"Kai" <yavin@gmx.com> wrote in message
news:drl62c$30k$1@utils.eclipse.org...
> Hey uses someone a xmlBlaster Client as OSGi bundle?
>
> My problem is that xmlBlaster creates its own class loader and tries to
> get the classpaths form the classloader which loaded the factory. I'm
> afraid they expect a URLClassloader but its the EclipseClassloader and I
> get a ClassCastException.
>
> Tips and tricks are welcome!

Previous Topic:	Equinox 3.2 based Application
Next Topic:	ClassNotFoundException in spite of working exports/imports?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Nov 05 22:17:35 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter