All...
I'm doing Java-first development on a service and the WSDL file being
generated (I'm using Tomcat v5.5 as my container with the CXFServlet) is
using arg0, arg1 etc. as the parameter names for my service methods rather
than using the actual parameter name specified in my Java code. Is this a
known shortcoming or am I doing something wrong? The WSDL isn't very
self-documenting with parameter names like this!
Here's an example wsdl snippet:
<xs:element name="moveItem" type="tns:moveItem"/>
<xs:complexType name="moveItem">
<xs:sequence>
<xs:element minOccurs="0" name="arg0" type="xs:string"/>
<xs:element minOccurs="0" name="arg1" type="xs:string"/>
<xs:element minOccurs="0" name="arg2" type="xs:string"/>
<xs:element minOccurs="0" name="arg3" type="xs:dateTime"/>
<xs:element minOccurs="0" name="arg4" type="xs:string"/>
<xs:element minOccurs="0" name="arg5" type="xs:string"/>
<xs:element minOccurs="0" name="arg6" type="xs:string"/>
</xs:sequence>
</xs:complexType>
Thanks,
Corey
--
View this message in context:
http://www.nabble.com/WSDL-method-parameter-names--tf4147851.html#a11799651
Sent from the cxf-user mailing list archive at Nabble.com.
