Hi Eduardo,
My understanding is this:
Java EE 5 Version 5.0, released May 2006 [JSR 244] specifies JAX-WS
2.0. See Chapter EE.6, Table EE.6-1 Java EE-Required Optional Packages.
JAX-WS 2.1 is a maintenance release that was completed well after the
Java EE 5 spec was finalized. So, how could Java EE 5 accomodate JAX-WS
2.1? Furthermore, the JAX-WS 2.1 spec seems to be in limbo (see warning
message here:
http://jcp.org/aboutJava/communityprocess/mrel/jsr224/index.html).
Am I wrong?
BTW, I think JAX-WS 2.1 is great. But, I'd still like to see a V2
GlassFish that is "pure Java EE 5" - i.e., code that runs on other Java
EE 5 implementations (e.g. SAP, BEA and the others that are coming
along) should be reasonably portable. But, because of WSIT
implementation, the WSDL generated by a JAX-WS 2.1 implementation, in
some cases, can be different from the JAX-WS 2.0 generated WSDL. I just
posted a question related to that issue on the jax-ws USER list. So,
you could have an @WebService, deployed on two different Java EE 5
"compliant" containers (one with JAX-WS 2.0 and the other with JAX-WS
2.1), generating different WSDL and requiring different Java SE client
code for invocation.
-- Mark
Eduardo Pelegri-Llopart wrote:
> Hi Mark -
>
> Can you clarify what do you mean by "Strictly Java EE 5 compliant"?
> The CTS for Java EE 5 allows for JAX-WS 2.1 (and JAXB 2.1).
>
> - eduard/o
>
> Mark Hansen wrote:
>
>> Are there any plans to release a GF 2.0 version that uses JAX-WS 2.0
>> instead of 2.1? The rationale for such a release would be to have a
>> V2 that is strictly Java EE 5 compliant.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>