FYI, the JDK6 Update3 is the last update which contain the jaxws api 2.0
and jaxb api 2.0,
the later release will contain the jaxws api 2.1 and jaxb api 2.1
http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21_in_jav.html
And another difference this is license, we use Apache 2.0
James
On Wednesday 10 October 2007, David W Sica wrote:
If JDK6 includes jaxws and jaxb jars what do I gain by using CXF over
just JDK6? If I do decide to use JDK6, can I get more details
regarding your response below on copying stuff to jre/lib?
Well, CXF supports a lot of things the JAX-WS implemention in JDK 6 does
not. Things like jms transports, advanced https configuration, Spring
configuration, WS-A, WS-RM, etc....
Let me clear about one thing:
CXF 2.0.x should work perfectly fine with JDK6. The api jars and such
that we ship are the same version as those built into JDK6.
The problem will be with CXF 2.1 which is our current development
mainline. For 2.1, we are targetting JAX-WS 2.1 which is newer than
what's in JDK6. To use the 2.1 snapshots, you'd most likely need to
copy the jaxb-* and jaxws-api-* jars (and maybe stax-api*) from our lib
directory to the jre/lib/endorsed dir. I'm not 100% sure as I haven't
tested it yet. At this point, I'm mostly working on fixes and stuff
still targetting 2.0.3 which should work fine for JDK6. (although I
don't have JDK6 installed to really test with yet)
Dan
Thanks,
David
On 10/4/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
Also, should I
pursue using JDK6 for deployment? Do I gain anything with JDK6 as
far as CXF is concerned?
I would not use jdk6 for right now. JDK6 is definitely going to
cause us problems on trunk. jk6 includes older versions of the
jaxws and jaxb jars which may conflict with the ones we require.
Thus, to work with jdk6, some stuff may need to be copied from our
lib dir to the jre/lib dir. We haven't spent much time
investigating that yet as trunk is still moving/changing pretty
fast. 2.0.2 SHOULD work OK with Java 6. It's mostly the new
stuff on trunk that will be a problem.
--
J. Daniel Kulp
