Eclipse Community Forums: BIRT » Designer plugin classloader exception

Home » Archived » BIRT » Designer plugin classloader exception(java.lang.IllegalArgumentException: interface com.sun.xml.ws.developer.WSBindingProvider is not visible from class loader)

Designer plugin classloader exception [message #1060165]

Thu, 23 May 2013 07:39

Eclipse User

Hi,
I have developed a scripted data set using JAVA. This dataset is using jax-ws to receive it's data. The dataset is working fine for me and can be used in our own server solution and also in Designer's preview.
Now in additon I have implemented a native RCP Eclipse plugin for uploading the design file to our server. The final jar is just copied to the Designer's plugin directory. This plugin is also using jax-ws and is also running fine.

But now I am running into a problem. When using preview and plugin at the same time without restarting Designer (e.g. running a preview and after that upload design file or the other way round), I'm running into an exception:

java.lang.IllegalArgumentException: interface com.sun.xml.ws.developer.WSBindingProvider is not visible from class loader

The problem seems to be that both implementations are using the same jar-dependencies (which are delivered twice, with dataset and plugin). But as far as I understood every Eclipse plugin should use its own classloader, so where is the problem? Does anyone has an idea whats to do?

Thank you a lot!

Note: I'm using Birt 4.2.2.

Best regards

Mark

Re: Designer plugin classloader exception [message #1060268 is a reply to message #1060165]

Thu, 23 May 2013 14:18

Eclipse User

Where do you put the jax-ws jar to fulfill the dependency on it by the Data Set?

Re: Designer plugin classloader exception [message #1060303 is a reply to message #1060268]

Fri, 24 May 2013 01:57

Eclipse User

I have placed the jar dependencies in the same directory as my dataset:
plugins\org.eclipse.birt.report.viewer_4.2.2.v201302041142\birt\scriptlib

Standalone without my additional RCP plugin this works fine.

My RCP-Plugin brings its own jar's with it, all bundled in the plugin.jar.

Re: Designer plugin classloader exception [message #1060639 is a reply to message #1060303]

Mon, 27 May 2013 08:35

Eclipse User

Any better places where libraries should be placed?

[Updated on: Mon, 27 May 2013 08:36] by Moderator

Re: Designer plugin classloader exception [message #1061042 is a reply to message #1060639]

Wed, 29 May 2013 12:04

Eclipse User

What happens if you remove the jar from the scriptlib folder? Does it find the jar in the plug-in to use and avoid the conflict?

Previous Topic:	Fiscal Report BIRT
Next Topic:	my parameter problem

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Mar 16 22:57:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter