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


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

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

Subject: Re: [sca-j] ISSUE 223: names in @WebParam/@WebResult


Pretty good - a tweak suggested inline...

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: Bryan Aupperle <aupperle@us.ibm.com>
To: sca-j@lists.oasis-open.org
Date: 30/11/2010 19:29
Subject: [sca-j] ISSUE 223: names in @WebParam/@WebResult

Proposed response:


Section 11.1 defines the effects on an SCA interface defined by a Java Interface or Java Class of any JAX-WS annotations on the Java Interface or Java Class or any of the elements of the Java Interface of Java Class.  It is important to define these effects since any remotable SCA interface is potentially mapped to WSDL 1.1 for testing interface compatibility so any an annotations that impact the
mapping of the Java to the corresponding WSDL portType and messages or any of the child elements of the corresponding portType and messages need to be considered.

SCA 1.1 considers the operations (including the name, return type and parameter types - but not names - of each operation) and faults/exceptions (including the structure of the fault message) when testing compatibility.

With this as background we can consider the treatment of the name/partName attributes of @WebParam and @WebReturn and compare this with the treatment of @WebFault, @RequestWrapper and @ResponseWrapper


The name and partName attributes of @WebParam and @WebReturn impact the name attribute of a part element of a WSDL message, which impacts the signature of the WSDL operation so this also impacts the signature of the SCA operation.  Admittedly this portion of the signature is not relevant in SCA 1.1, but defining the impacts sets the path for potential future refinement.  Because parameter names are not currently used, there are no normative statements associated withe the impacts of the name and partName attributes of @WebParam and @WebReturn.

Contrast this with effects of @WebFault, @RequestWrapper and @ResponseWrapper which control the XML information with respect to the corresponding JAXB beans but not the operation/fault names or message content and thus not the signature of a operation or fault.

This section could perhaps be clearer about the name and partName attributes of @WebParam and @WebReturn not currently having any observable impact on the SCA interface, but the information in the tables is correct and appropriate.


Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

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]