Re: [sca-j-comment] comment on @WebParam/@WebResult

[Scott Kurz <skurz@us.ibm.com>]

Mike,

So what is the purpose of calling attention
to this, as opposed to say @WebFault/@RequestWrapper/@ResponseWrapper for
which we don't say anything special for SCA but just defer to JAX-WS?

Why do we need to know the "parameter
name" mapped to?  Is it just for describing the serialization?

I'd imagine @WebParam/@WebResult could
be important for specifying serialization details for an XML wireformat.
   But so could the three above, in a similar manner.  The
@SOAPBinding can be important in this regard too, since it can be used
to signify the presence or absence of the doc-lit-wrapped wrapper. 

So are we mentioning @WebParam/@WebResult
simply to emphasize the point (in which case we could have emphasized the
same for the other annotations I mentioned, but just didn't bother) ?  
Or is there some other reason to mention the mapping to "parameter
name" for some more abstract purpose (or another specific one)?

Regards,

Scott Kurz



From:      
 Mike Edwards <mike_edwards@uk.ibm.com>
To:      
 Scott Kurz/Poughkeepsie/IBM@IBMUS,
sca-j-comment@lists.oasis-open.org
Date:      
 11/25/2010 03:55 AM
Subject:    
   Re: [sca-j-comment]
comment on @WebParam/@WebResult

---

Scott, 

In relation to the whole of that section, for items like "Sets parameter
name" this is *always* talking about the mapping to
WSDL - that is what these JAX-WS annotations are all about.

You are right in saying that the Java is what it is, but the WSDL mapped
from that Java is what is at issue here - and 
nominally, SCA is working off that WSDL mapping. 


Yours, Mike

Dr Mike Edwards		Mail Point 146, Hursley Park
STSM		Winchester, Hants SO21 2JN
SCA & Services Standards		United Kingdom
Co-Chair OASIS SCA Assembly TC
IBM Software Group
Phone:	+44-1962 818014
Mobile:	+44-7802-467431 (274097)
e-mail:	mike_edwards@uk.ibm.com

From:	Scott Kurz <skurz@us.ibm.com>
To:	sca-j-comment@lists.oasis-open.org
Date:	24/11/2010 16:03
Subject:	[sca-j-comment] comment on @WebParam/@WebResult

---

This is a small point but... 

I was looking over section: 
11.1 JAX-WS Annotations and SCA Interfaces 
and thinking maybe there is no point in calling out 'name' and 'partName'
for @WebParam/@WebResult as specially affected from the SCA perspective.
  

The parameter name is already in the Java, so saying "Sets
parameter name" implies
that this is a parameter name to be used for some other SCA purpose.  
  E.g. the fact that 'operationName' is called out on @WebMethod implies
that, as the SCA operation name, this is the value that will be used for
something like interface compatibility comparison and operation selection
on the JMS binding.   

Maybe I just don't understand what this other purpose is... I'm pretty
sure it doesn't matter for interface compatibility comparison.    
 Or maybe it just slipped in but isn't needed.

----- 

On a separate but related note, it's interesting that JAX-WS 2.2 went and
added the option of using @XmlElement in place of @WebParam, (I might be
slightly misphrasing that), which is a tighter integration with JAXB rather
than a looser one which can be used with JAXB or SDO.   So,  in
not having to consider that, 2.1 was a cleaner level for us to base on,

Regards, 

Scott Kurz

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU