[jira] Resolved: (TUSCANY-2579) Tuscany Schemas use sequences which makes the composite elements to have order, while that is not the case with Spec

["Dan Becker (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Becker resolved TUSCANY-2579.
---------------------------------

    Resolution: Won't Fix

OSOA closed this issue with no action and will not update the spec here. Since Tuscany must follow the OSOA spec for this issue, we cannot add choice and must follow java.implementation in the same order as OSOA specs.

> Tuscany Schemas use sequences which makes the composite elements to have order, while that is not the case with Spec
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2579
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2579
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Problem Determination
>         Environment: All
>            Reporter: Hasan Muhammad
>             Fix For: Java-SCA-Next
>
>
> The schema for component is as such:
>     <element name="componentType" type="sca:ComponentType"/>
>     <complexType name="ComponentType">
>     	<sequence>
>              <choice minOccurs="0" maxOccurs="1">
> 	             <element ref="sca:implementation"/>
> 	             <any namespace="##other" processContents="lax"/>
>              </choice>
>         	<choice minOccurs="0" maxOccurs="unbounded">
>             	<element name="service" type="sca:ComponentService" />
>             	<element name="reference" type="sca:ComponentReference"/>
>             	<element name="property" type="sca:Property"/>
>         	</choice>
>         	<!-- 
>         	<any namespace="##other" processContents="lax" minOccurs="0" 
>         		maxOccurs="unbounded"/>
>         	-->
>         </sequence>
>         <attribute name="constrainingType" type="QName" use="optional"/>
>         <anyAttribute namespace="##any" processContents="lax"/>
>     </complexType>
> This forces the user to have the element "implementation.java" before the other elements such as service, reference etc, which should not be the case. The following error is generated
> alidatingXML E   XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-complex-type.2.4.a: Invalid content was found starting with element 'implementation.java'. One of '{"http://www.osoa.org/xmlns/sca/1.0":service, "http://www.osoa.org/xmlns/sca/1.0":reference, "http://www.osoa.org/xmlns/sca/1.0":property}' is expected.
> So the schema needs to be changed. This problem may exist at other places in this schema and other schemas as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.