Both of them should have been generated as arg0/arg1. Not sure why the
BARE mode would have been different.
In anycase, the sollution is to annotate the params with @WebParam
annotations:
public java.lang.String sayHi(
@WebParam(name = "text" java.lang.String text,
@WebParam(name = "info" demo.spring.ProfileInfo info
);
Dan
On Wednesday 09 January 2008, yulinxp wrote:
> The wsdl generated using SOAPBinding.ParameterStyle.BARE will have
> "text/info" as parameter name,
> while wsdl generated using wrapped only shows arg0/arg1. Then when
> writing the client code, I will see (String arg0,...) when using
> Eclipse parameter hit.
>
> Is there a way to make wrapped wsdl use parameter name instead of
> arg01?
>
> //interface
> public interface HelloWorld {
> public java.lang.String sayHi(
> java.lang.String text, demo.spring.ProfileInfo info
> );
> }
>
> //bare
>
> <xs:element name="text" nillable="true" type="xs:string"/> <--------
> name="text"
> <xs:element name="info" nillable="true" type="profileInfo"/>
> <-------- name="info"
>
> <wsdl:message name="sayHi">
> <wsdl:part name="text" element="tns:text"></wsdl:part>
> <wsdl:part name="info" element="tns:info"></wsdl:part>
> </wsdl:message>
>
> <wsdl:portType name="HelloWorld">
> <wsdl:operation name="sayHi">
> <wsdl:input name="sayHi" message="tns:sayHi"></wsdl:input>
> </wsdl:operation>
> </wsdl:portType>
>
>
> //wrapped
>
> <xsd:element name="sayHi" type="tns:sayHi"/>
> <xsd:complexType name="sayHi">
> <xsd:sequence>
> <xsd:element minOccurs="0" name="arg0" type="xsd:string"/>
> <--------
> name="arg0"
> <xs:element minOccurs="0" name="arg1"
> type="profileInfo"/> <-------- name="arg1"
> </xsd:sequence>
> </xsd:complexType>
>
> <wsdl:message name="sayHi">
> <wsdl:part name="parameters" element="tns:sayHi">
> </wsdl:part>
>
> <wsdl:portType name="HelloWorld">
> <wsdl:operation name="sayHi">
> <wsdl:input name="sayHi" message="tns:sayHi"></wsdl:input>
> </wsdl:operation>
> </wsdl:portType>
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
