Well, there is a few things to be considered:
* The jax-ws 2.1 additions are not removed, the stack will
still be able to consume it
* They moved to a separate jar (JDK 6 endorsed requires it).
That means client that rely on 2.1 API need update their
class-path
* It breaks compatibility for those client that rely on
JAX-WS artifacts that exist in two versions, i.e. Service.
* However this deals with WebServiceFeature and
EndpointReference. I don't believe many people used it,
since WebServiceFeature was non-functional.
But yes, you are right. It breaks backwards compatibility in
a few places.
View the original post : http://www.jboss.com/index.html?
module=bb&op=viewtopic&p=4089203#4089203
Reply to the post : http://www.jboss.com/index.
html?module=bb&op=posting&mode=reply&p=4089203
_______________________________________________
jboss-dev-forums mailing list
jboss-dev-forums lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-dev-foru
ms
|
