You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Bruno Delzant (JIRA)" <ji...@apache.org> on 2009/01/19 12:48:00 UTC
[jira] Updated: (AXIS2-4214) Code generation for handling several
"part" element in element "message" in WSDL leads to incorrect ordering in
generated code
[ https://issues.apache.org/jira/browse/AXIS2-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruno Delzant updated AXIS2-4214:
---------------------------------
Attachment: Ppm_createResponse.java
Error for ordering between lines 570 and 632
> Code generation for handling several "part" element in element "message" in WSDL leads to incorrect ordering in generated code
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4214
> URL: https://issues.apache.org/jira/browse/AXIS2-4214
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.4.1, 1.4
> Environment: Windows, Java 1.6
> Reporter: Bruno Delzant
> Attachments: creactor_example.wsdl, Ppm_createResponse.java
>
>
> Hi,
> when WSDL contain a message with several parts like this
> <message name="ppm_createResponse">
> <part name="returnValue" type="xsd:int" />
> <part name="returnComment" type="xsd:string" />
> <part name="accounid" type="xsd:string" />
> <part name="identify" type="xsd:string" />
> </message>
> then the ADB code generated does not respect the ordering of the parts. It generate code that handles parameter in different order and so it leads to UnexpectedElement error.
> I think the problem is in the file org.apache.axis2.schema.template.ADBBeanTemplate.xsl
> See my WSDL input and generated class where the ordering is incorrect (Class osp_methods.Ppm_createResponse, order problem from line 570 to 632)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.