[jira] Closed: (GERONIMO-3080) Axis2: Improve AxisServiceGenerator to handle more than 1 parameter of a service method (doclitwrapped case)

["Lin Sun (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun closed GERONIMO-3080.
-----------------------------


This prob has been addressed with the updated code.  Verified the calculator sample works.

> Axis2: Improve AxisServiceGenerator to handle more than 1 parameter of a service method (doclitwrapped case)
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-3080
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3080
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0-M5
>         Environment: sun 1.5 SDK + Win XP
>            Reporter: Lin Sun
>             Fix For: 2.0-M5
>
>         Attachments: G3080.patch
>
>
> The AxisServiceGenerator can only handle one parameter of the service method.  For example, from the calculatorservice.wsdl:
>              <xsd:element name="add">
>                 <xsd:complexType>
>                    <xsd:sequence>
>                       <xsd:element name="value1" type="xsd:int"/>
>                       <xsd:element name="value2" type="xsd:int"/>
>                    </xsd:sequence>
>                 </xsd:complexType>
>              </xsd:element>
> This add method contains 2 params however the AxisServiceGenerator would only create 1 ParameterDescriptionComposite, which is the one for value1.   The fix is to build the ParameterDescriptionComposite inside of the while loop for doclitwrapped case.
> With the fix, I am able to get the calculatorservice.add invoked and see value1 and value2 printed on the server.   However, end to end flow still doesn't work (due to a NPE from Axis2) and currently look into that to see if it is an Axis2 issue or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.