xsd:choice with nested xsd:sequence generates code as though xsd:sequence with
nested xsd:choice
------------------------------------------------------------------------------------------------
Key: AXISCPP-876
URL: http://issues.apache.org/jira/browse/AXISCPP-876
Project: Axis-C++
Type: Bug
Components: Serialization
Reporter: Manohar
Hi,
I've defined a complex type as
<xsd:complexType name="aRecord">
<xsd:choice>
<xsd:sequence>
<xsd:element name="field1" type="xsd:string"
minOccurs="0" nillable="false"/>
<xsd:element name="field2" type="xsd:string"
minOccurs="0" nillable="false"/>
</xsd:sequence>
<xsd:element name="field3" type="xsd:string" nillable="false"/>
<xsd:element name="field4" type="xsd:string" nillable="false"/>
</xsd:choice>
</xsd:complexType>
and trying to send aRecord object as part of request message and receive the
same in return.
Here is the serialize code generated for the above choice object:
/* then serialize elements if any*/
pSZ->serializeAsElement("field1", Axis_URI_aRecord,
(void*)(param->field1), XSD_STRING);
pSZ->serializeAsElement("field2", Axis_URI_aRecord,
(void*)(param->field2), XSD_STRING);
if(param->field3)
{
pSZ->serializeAsElement("field3", Axis_URI_aRecord,
(void*)(param->field3), XSD_STRING);
}
else if(param->field4)
{
pSZ->serializeAsElement("field4", Axis_URI_aRecord,
(void*)(param->field4), XSD_STRING);
}
>From this it appears that, it's acted as though we have a choice within a
>sequence, rather than a sequence within a choice.
Regards
Manohar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
