OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]