This is a summary of the changes made to accomodate JAXWS and JAXB 2.2
apis in v3.
V3 contains jaxb-api-osgi.jar which has jaxb 2.2 apis and
webservices-api-osgi.jar which has JAXWS 2.2 apis.
JDK 6Ux has JAXWS and JAXB 2.1 apis. On the server side there is no
impact these two api jars are loaded as regular osgi modules and JAXWS
2.2 and JAXB 2.2 api classes from these jars override the ones of the JDK
For standalone clients they will need to set java.endorsed.dirs to the
folder containing these jars.
From today jaxb-api-osgi.jar and webservices-api-osgi.jar are moved to
modules/endorsed in the full glassfish distribution.
For web distribution only jaxb-api-osgi.jar will be in modules/endorsed
(Webservices support is not in by default and needs to be installed by
UC, upon installation webservices-api-osgi.jar will also be installed in
modules/endorsed)
So standalone clients the clients will need to set java.endorsed.dirs to
glassfishv3/glassfish/modules/endorsed folder. The same applies for tcks
tests.
For wsimport/wsgen ant tasks you will need to set the xendorsed=true and
have these 2.2 api jars in classpath so that it can work 2.2 based
artifacts.
I have modified the scripts and QL and glassfish samples to incorporate
these changes and we will document these. This will also take care of
https://glassfish.dev.java.net/issues/show_bug.cgi?id=7853
Regards,
Bhakti