Hi Guys,
I've seen a number of posts regarding similar issues, none of which answers
my question exactly.
Here's the situation:
My application is developed using the Eclipse plugin framework. One of my
plugins is using xFire client to talk to a web service using code similar
to this:
Service serviceModel = new
ObjectServiceFactory().create(MyService.class);
XFireProxyFactory serviceFactory = new XFireProxyFactory();
MySevice myService = (MyService)
serviceFactory.create(serviceModel, url);
myService.callMyMethod();
The last line triggers the following exception:
I understand why this is happening - the code is being called from the AWT
thread (initialised from a different plugin & thus having a different class
loader) and the way to resolve this is to move the call onto a backround
thread from my class so getting my class loader. But, what if I want to
run the job on a system background thread that already exists & is created
by another plugin?
I guess what I'm asking is:
is there anyway to programmatically tell xFire to use a specific
classloader instead of using the the thread's context class loader?
thanks in advance for your time,
Brian Hobbs
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
