I agree with Russell.
JSR 101 v1.0 clearly indicates that the parameters of the signature are
obtained from the message parts. This information is used to determine
order, holders, etc. There is no mention of unwrapping an part's element=
attribute to populate the parameter list.
What if the complexType TradePriceRequest contained two elements
(tickerSymbol and companyName) ? Would the TCK expect the following
signature:
public float getLastTradePrice(String body, String body) throws
RemoteException; // NOTE Two Parameters with the same name!
Rich 'Shirley' Scheuerle
IBM WebSphere & Axis Web Services Development
512-838-5115 (IBM TL 678-5115)
Russell Butek/Austin/IBM@IBMUS
06/14/2002 12:34 PM
Please respond to axis-dev
To: [EMAIL PROTECTED]
cc:
Subject: TCK question: .NET wrapped style?
Here's a WSDL snippet from the TCK:
<element name="TradePriceRequest">
<complexType>
<sequence>
<element name="tickerSymbol" type="string"/>
</sequence>
</complexType>
</element>
<element name="TradePrice">
<complexType>
<sequence>
<element name="price" type="float"/>
</sequence>
</complexType>
</element>
<message name="GetLastTradePriceInput">
<part name="body" element="xsd1:TradePriceRequest"/>
</message>
<message name="GetLastTradePriceOutput">
<part name="body" element="xsd1:TradePrice"/>
</message>
<portType name="StockQuotePortType">
<operation name="GetLastTradePrice">
<input message="tns:GetLastTradePriceInput"/>
<output message="tns:GetLastTradePriceOutput"/>
</operation>
</portType>
(the binding for this WSDL is doc/lit). This is ALMOST like .NET's doc/lit
style. But it's not quite. So we generate:
public TradePrice getLastTradePrice(TradePriceRequest body) throws
RemoteException;
Unfortunately the TCK expects the following signature:
public float getLastTradePrice(String body) throws RemoteException;
I don't read anything in JAX-RPC that allows or requires this signature,
so I do not believe the TCK should expect this signature. Can anyone tell
me I'm wrong?
Russell Butek
[EMAIL PROTECTED]
