[ http://issues.apache.org/jira/browse/AXIS2-724?page=comments#action_12402227 ]
Chuck Williams commented on AXIS2-724: -------------------------------------- This has a very simple fix, which is to use the <choice>-specific template code for <all>. This was the intent, as noted in the template comment that <all> and <choice> are order-independent, while <sequence> is order-dependent. Unfortunately, the <all> test was not included. I'd be happy to make the change if not already underway. > [ADB] xsd:all deserialization should support out-of-order elements > ------------------------------------------------------------------ > > Key: AXIS2-724 > URL: http://issues.apache.org/jira/browse/AXIS2-724 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > > Please see modules\integration\test\samples\wsdl\bench\Benchmark.wsdl. It has > a construct > <xsd:all> > <xsd:element name="x" type="xsd:int"/> > <xsd:element name="y" type="xsd:int"/> > <xsd:element name="value" > type="xsd:double"/> > </xsd:all> > The xsd:all element specifies that the child elements can appear in any order > and that each child element can occur zero or one time. > If the soap message has the wrong order (say value then x then y) , the > generated deserialzation code throws runtime exception. > thanks, > dims -- 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
