Eclipse RCP classloading problem with Metro?

For anyone else who runs into this problem, I was able to find a solution. I added the metro jars, along with the config directory containing my wsit configuration files, to the JVM's boot classpath using these JVM options.

For anyone else who runs into this problem, I was able to find a solution. I added the metro jars, along with the config directory containing my wsit configuration files, to the JVM's boot classpath using these JVM options: -Xbootclasspath/a:. /lib/webservices-api.

Jar -Xbootclasspath/a:. /lib/webservices-rt. Jar -Xbootclasspath/a:.

/lib/webservices-tools. Jar -Xbootclasspath/a:. /config The webservices-api.

Jar no longer needs to be in $JAVA_HOME/jre/lib/endorsed for this to work. It is certainly not the normal Eclipse model, but this is the only way I have found to use Metro within an Eclipse RCP application with Java 1.6.

Java SE 6 already includes metro. It includes jax-ws 2.0, so you can remove those jars completely. Only if you have specific need to use jax-ws 2.1 together with java SE 6, you can follow the instructions here -> https://jax-ws.dev.java.Net/faq/index.

Html EDIT: You are right about your last comment. Code placed in the endorsed folder is loaded with the endorsed class loader, so it can't find classes that are located in the plugins. I suggest that you put the all the metro jars in the endorsed dir.

This way they'll be available not only for your plug-in, but for the entire VM.

The problem is that the Java SE 6 version of JAX-WS does not implement security. I have tried removing the metro jars as you suggest, in which case I get past the error above but then I get an error back from the server complaining that my client did not include a security header (confirming that the JDK version of JAX-WS does not implement security). So I think I really need to use the Metro version of JAX-WS in order to implement security.

– Jeff Jan 20 '10 at 17:31 are you sure about the lack of security? The guide clearly says "Java SE 6 Update Release 4 and later already contain the JAX-WS 2.1 API and the following work around is not necessary anymore" – Yoni Jan 20 '10 at 17:46 Regarding your edit, the Metro site explicitly states that only the webservices-api. Jar should go into the endorsed directory, and none of the other jars.

Nevertheless, I did try putting the other metro jars in the endorsed directory. When I do, I start getting strange LinkageErrors. Regarding the lack of security, I read that in another online forum.

That doesn't mean it's true of course, but when I attempt to run without any metro jars, the client runs but does not include a security header in the request (confirmed by the error returned from the server and tcpmon). – Jeff Jan 20 '10 at 18:38.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.