issue with Multipart message in response --- Is this a bug ??

[rahul yadav <ra...@gmail.com>]

Hi All,
   I am using attached WSDL to generate java source with
org.apache.axis2.wsdl.codegen.CodeGenerationEngine class using ADB binding.
It is successfully able to generate the java source but on calling web
service i get an exception reporting  invalid sub-element
"STD_Types_INT2_outReturn". I have checked the SOAP request and response
message both looks in shape.




WSDL is rpc/enc and has multipart message in couple of operation response.
Here are few lines from wsdl...

<wsdl:message name="STD_Types_INT2_outRequest">
<wsdl:part name="int2" type="xsd:int"/>
</wsdl:message>

<wsdl:message name="STD_Types_INT2_outResponse">
<wsdl:part name="STD_Types_INT2_outReturn" type="xsd:int"/>
<wsdl:part name="int2" type="xsd:int"/>
</wsdl:message>

<wsdl:operation name="STD_Types_INT2_out" parameterOrder="int2">
<wsdl:input message="impl:STD_Types_INT2_outRequest"
name="STD_Types_INT2_outRequest"/>
<wsdl:output message="impl:STD_Types_INT2_outResponse"
name="STD_Types_INT2_outResponse"/>
</wsdl:operation>

Exception is thrown from the code generated by Axis2, that do parsing of
SOAP response to Java Object this is done by a method of generated Stub
class(attached herewith)..

 java.lang.Object fromOM(org.apache.axiom.om.OMElement param,java.lang.Class
type, java.util.Map extraNamespaces) throws org.apache.axis2.AxisFault

Looking at the parser code, i can make out that parser excepts "int2" to be
the first element/parameter in Soap body but SOAP message has
"STD_Types_INT2_outReturn" as first parameter as evident from wsdl leading
to failure of parser. WSDL specification does not define parameterOrder for
out message  giving space to confusion of parsing  SOAP response to Java
object.
Will i be right to say that this is a bug in Axis2 ? If "no" what is the way
out and if "yes" when can i expect it to be fixed, i have a major release on
calender, quick response is highly appriciated.

Thanks,
Rahul Yadav