I am sick of the fun that is getting JAX-WS 2.1 to work on JVM 1.6.
Oh, copy these four jars into the endorsed directory and then you can use JAX-WS 2.1... oh but sometimes it won't work for some unknown reason and then it will work again.
How you are supposed to explain this to end users, I don't know.
So next you need a platform specific installer to put those jars into the correct location, or a platform specific start script to tell the JVM about my alternate endorsed lib folder... or do I write a self-extracting jar file that exctracts the libs and forks a second JVM... no that won't work for people wanting to use my library..
We went through all this pain with SAX and DOM. Did Sun learn nothing?
The instructions to run on top of Java SE 6 are documented at: https://jax-ws.dev.java.net/nonav/2.1.2rc1/docs/ReleaseNotes.html#Running_on_top_of_JDK_6.
ReplyDeleteCan you provide more details on what did not work for you ?
-Arun
And help is on the way... we are putting JAX-WS 2.1 on JDK6u4.
ReplyDeleteArun,
ReplyDeleteThe instructions worked... sort of...
In ways that I cannot reproduce, some times the endorsed versions fail to show up.
In ways that I can reproduce, when running jetty with maven2, reloading the container, and JAX-WS jumps back to 2.0... even though I have the 2.1 on the class path and in the endorsed directory.
Kohsuke!
ReplyDeleteDid not realise you were reading my blog!
Yeah, roll on JDK 6u4... maybe they'll have fixed the Hudson circular generics references problem with javac on non-windows platforms!