[
https://issues.apache.org/jira/browse/TUSCANY-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480748
]
Frank Budinsky commented on TUSCANY-1168:
-----------------------------------------
Raymond,
Yes, you are right. I think there are a few examples of this problem. I think
we never noticed before, because prior to TUSCANY-521 there was an exposed
sequence property anyway (now it's hidden). I'll fix this and TUSCANY-1169 at
the same time.
Frank.
> Type.isSequenced() returns wrong value for my XSD
> -------------------------------------------------
>
> Key: TUSCANY-1168
> URL: https://issues.apache.org/jira/browse/TUSCANY-1168
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-SDO-M3
> Reporter: Raymond Feng
>
> For the following XSD:
> <schema targetNamespace="http://www.example.com/wrapper";
> xmlns="http://www.w3.org/2001/XMLSchema";>
> <!-- Faults -->
> <element name="op">
> <complexType>
> <sequence maxOccurs="unbounded">
> <element name="message" minOccurs="1" type="string" />
> <element name="symbol" minOccurs="1" maxOccurs="3"
> type="string" />
> </sequence>
> </complexType>
> </element>
> <element name="opResponse">
> <complexType>
> <sequence maxOccurs="1">
> <element name="price" minOccurs="1" maxOccurs="unbounded"
> type="string" />
> </sequence>
> </complexType>
> </element>
> </schema>
> I assume the type for "op" element is sequenced since maxOccurs >1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
