You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/08/23 08:33:13 UTC
[jira] Created: (TUSCANY-659) Position of not consistent
between composite, component and componentType
Position of <property> not consistent between composite, component and componentType
------------------------------------------------------------------------------------
Key: TUSCANY-659
URL: http://issues.apache.org/jira/browse/TUSCANY-659
Project: Tuscany
Issue Type: Bug
Components: Specification
Affects Versions: Cpp-current
Reporter: Jean-Sebastien Delfino
Assigned To: Jean-Sebastien Delfino
In a composite properties are defined after services and before components and before references.
In component and componentType properties appear after references.
This is confusing, the position of properties should be consistent between composites, components and componentTypes.
I will raise that issue to the OSOA spec workgroup.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-659) Position of not
consistent between composite, component and componentType
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466411 ]
Jean-Sebastien Delfino commented on TUSCANY-659:
------------------------------------------------
Correction, this was SCA spec issue #142
Here are the detailed changes to the XSD:
In all complex types using sequence, use an unbounded choice where
possible. (Note: this is going a bit beyond the particular complex
types that can contain <property> elements, for consistency's sake.)
This has the following specific implications for the ComponentType,
Composite, Service, Reference, and Component complex types:
----
Replace:
<complexType name="ComponentType">
<sequence>
<element minOccurs="0" maxOccurs="unbounded"
name="service" type="sca:Service"/>
<element minOccurs="0" maxOccurs="unbounded"
name="reference" type="sca:Reference"/>
<element minOccurs="0" maxOccurs="unbounded"
name="property" type="sca:Property"/>
<any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
with:
<complexType name = "ComponentType">
<choice minOccurs = "0" maxOccurs = "unbounded">
<element name = "service" type = "sca:Service" />
<element name = "reference" type = "sca:Reference"/>
<element name = "property" type = "sca:Property"/>
<any namespace = "##other" processContents = "lax"/>
</choice>
----
Replace:
<complexType name="Composite">
<sequence>
<element minOccurs="0" maxOccurs="unbounded"
name="include" type="anyURI"/>
<element minOccurs="0" maxOccurs="unbounded"
name="service" type="sca:Service"/>
<element minOccurs="0" maxOccurs="unbounded"
name="property" type="sca:Property"/>
<element minOccurs="0" maxOccurs="unbounded"
name="component" type="sca:Component"/>
<element minOccurs="0" maxOccurs="unbounded"
name="reference" type="sca:Reference"/>
<element minOccurs="0" maxOccurs="unbounded" name="wire"
type="sca:Wire"/>
<any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
with:
<complexType name = "Composite">
<sequence>
<element name = "include" type = "anyURI" minOccurs =
"0" maxOccurs = "unbounded"/>
<choice minOccurs="0" maxOccurs="unbounded">
<element name = "service" type = "sca:Service"/>
<element name = "property" type = "sca:Property"/>
<element name = "component" type = "sca:Component"/>
<element name = "reference" type = "sca:Reference"/>
<element name = "wire" type = "sca:Wire"/>
<any namespace = "##other" processContents = "lax"/>
</choice>
</sequence>
----
Replace:
<complexType name="Service">
<sequence>
<element ref="sca:interface" minOccurs="1" maxOccurs="1"/>
<element ref="sca:binding" minOccurs="0"
maxOccurs="unbounded"/>
<element name="reference" minOccurs="0"
maxOccurs="unbounded" type="anyURI"/>
<any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
with:
<complexType name = "Service">
<sequence>
<element ref = "sca:interface"/>
<choice minOccurs = "0" maxOccurs = "unbounded">
<element ref = "sca:binding"/>
<element name = "reference" type = "anyURI"/>
<any namespace = "##other" processContents = "lax"/>
</choice>
</sequence>
(and the identical change for "Reference")
----
Replace:
<complexType name="Component">
<sequence>
<element ref="sca:implementation" minOccurs="0"
maxOccurs="1"/>
<element name="reference" type="sca:ReferenceValue"
minOccurs="0" maxOccurs="unbounded"/>
<element name="property" type="sca:Property"
minOccurs="0" maxOccurs="unbounded"/>
<any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
with:
<complexType name = "Component">
<sequence>
<element ref = "sca:implementation" minOccurs = "0"/>
<choice minOccurs = "0" maxOccurs = "unbounded">
<element name = "reference" type =
"sca:ReferenceValue"/>
<element name = "property" type = "sca:Property" />
<any namespace = "##other" processContents = "lax"/>
</choice>
</sequence>
> Position of <property> not consistent between composite, component and componentType
> ------------------------------------------------------------------------------------
>
> Key: TUSCANY-659
> URL: https://issues.apache.org/jira/browse/TUSCANY-659
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
> Affects Versions: Cpp-current
> Reporter: Jean-Sebastien Delfino
> Assigned To: Jean-Sebastien Delfino
> Fix For: Cpp-M3
>
>
> In a composite properties are defined after services and before components and before references.
> In component and componentType properties appear after references.
> This is confusing, the position of properties should be consistent between composites, components and componentTypes.
> I will raise that issue to the OSOA spec workgroup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-659) Position of not consistent
between composite, component and componentType
Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-659?page=all ]
ant elder updated TUSCANY-659:
------------------------------
Fix Version/s: Cpp-current
> Position of <property> not consistent between composite, component and componentType
> ------------------------------------------------------------------------------------
>
> Key: TUSCANY-659
> URL: http://issues.apache.org/jira/browse/TUSCANY-659
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
> Affects Versions: Cpp-current
> Reporter: Jean-Sebastien Delfino
> Assigned To: Jean-Sebastien Delfino
> Fix For: Cpp-current
>
>
> In a composite properties are defined after services and before components and before references.
> In component and componentType properties appear after references.
> This is confusing, the position of properties should be consistent between composites, components and componentTypes.
> I will raise that issue to the OSOA spec workgroup.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-659) Position of not
consistent between composite, component and componentType
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino resolved TUSCANY-659.
--------------------------------------------
Resolution: Fixed
This has been fixed by SCA spec issue #126. The order of services/references/properties has now been relaxed.
> Position of <property> not consistent between composite, component and componentType
> ------------------------------------------------------------------------------------
>
> Key: TUSCANY-659
> URL: https://issues.apache.org/jira/browse/TUSCANY-659
> Project: Tuscany
> Issue Type: Bug
> Components: Specification
> Affects Versions: Cpp-current
> Reporter: Jean-Sebastien Delfino
> Assigned To: Jean-Sebastien Delfino
> Fix For: Cpp-M3
>
>
> In a composite properties are defined after services and before components and before references.
> In component and componentType properties appear after references.
> This is confusing, the position of properties should be consistent between composites, components and componentTypes.
> I will raise that issue to the OSOA spec workgroup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org