Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

axis2 element order sequence

 
you leak tan
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

Need help asap:

For WSDLi using ADB

<xs:complexType name="SubjectSegment">
<xs:sequence>
<xs:element minOccurs="0" name="applicationSegmentId" type="xs:string"/>
<xs:element minOccurs="0" name="subSegAtt" type="tns:SubjectSegmentSubjectSegmentAttrs"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="empSeg" nillable="true" type="tns:SubjectSegmentEmploymentSegment"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="incSeg" nillable="true" type="tns:SubjectSegmentIncomeSegment"/>
<xs:element minOccurs="0" name="relSeg" type="tns:SubjectSegmentRelationshipSegment"/>
<xs:element minOccurs="0" name="reaSeg" type="tns:SubjectSegmentRealSavingsPlanSegment"/>
</xs:sequence>
</xs:complexType>


but the response from sever return as below:


<return>
<applicationSegmentId/>
<empSeg />
<incSeg />
<reaSeg />
<relSeg />
<subSegAtt>
</return>


How come the order is a to z for element name?
How to make it as below:

<return>
<applicationSegmentId/>
<subSegAtt>
<relSeg />
<reaSeg />
<empSeg />
<incSeg />
</return>


Very thanks for reply to help

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic