[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-j-comment] comment on @WebParam/@WebResult
This is filed as issue 223 [1]. -Anish -- [1] http://osoa.org/jira/browse/JAVA-223 On 11/24/2010 7:57 AM, Scott Kurz wrote: > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]