axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vikas charak (JIRA)" <>
Subject [jira] Commented: (AXIS2-1312) Issue with method parameter names in WSDL file genarted by Java2WSDLTask
Date Thu, 12 Oct 2006 14:12:35 GMT
    [ ] 
vikas charak commented on AXIS2-1312:

I did some more tests and found that this is a issue if you specify an interface in Java2WSDLTask

{ className="com.test.IntrfcUserService"}.
The parameter names are fine in case you use the implementation class.

> Issue with method parameter names in WSDL file genarted by Java2WSDLTask
> ------------------------------------------------------------------------
>                 Key: AXIS2-1312
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: wsdl
>    Affects Versions: nightly
>         Environment: Windows XP
> Axis2 Nightly of Sep-27-2006
>            Reporter: vikas charak
>            Priority: Minor
>         Attachments:,, UserService.wsdl
> When I generate WSDL file using Java2WDLTask , everything looks okay other than the name
of the method  parameters.
> In my service I have the following method
> User getUser(String userID). 
> Look at the following WSDL snippet. I was expecting "userID" to be in place of "param0".

> [Although its not a big issue but then you need to take an extra step of  changing the
parameter name,  so that the consumer of the web service can understand what should be passed
as input parameter. So in this case a userID instead of param0]
> <xs:element name="getUser">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="param0" type="xs:string" />
> </xs:sequence>
> </xs:complexType>
> Interesting this is it did translate complex type User accurately as follows
> <xs:complexType name="User">
> <xs:sequence>
> <xs:element name="firstName" type="xs:string" />
> <xs:element name="lastName" type="xs:string" />
> </xs:sequence>
> </xs:complexType>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message