[
https://issues.apache.org/jira/browse/TUSCANY-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513257
]
Mike Edwards commented on TUSCANY-1443:
---------------------------------------
Umm, which SCA XSDs are you referencing here?
The correct ones are in the SCA Assembly spec document here:
http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V100.pdf
and they are also available directly on the web at their indicated locations,
eg:
http://www.osoa.org/xmlns/sca/1.0
In those, the definition of SCA Property type goes like this:
<complexType name="SCAPropertyBase" mixed="true">
<!-- mixed="true" to handle simple type -->
<sequence>
<any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="1" />
<!-- NOT an extension point; This xsd:any exists to accept
the element-based or complex type property
i.e. no element-based extension point under
"sca:property" -->
</sequence>
</complexType>
<!-- complex type for sca:property declaration -->
<complexType name="Property" mixed="true">
<complexContent>
<extension base="sca:SCAPropertyBase">
<!-- extension defines the place to hold default value -->
<attribute name="name" type="NCName" use="required"/>
<attribute name="type" type="QName" use="optional"/>
<attribute name="element" type="QName" use="optional"/>
<attribute name="many" type="boolean" default="false"
use="optional"/>
<attribute name="mustSupply" type="boolean" default="false"
use="optional"/>
<anyAttribute namespace="##any" processContents="lax"/>
<!-- an extension point ; attribute-based only -->
</extension>
</complexContent>
</complexType>
...which I believe covers the usage described for the property in the composite
document which you reference.
Now, there is a problem with the XSDs within the cpp Project, but it isn't the
one you've raised. Actually, the ones in the cpp project look to be out of
date and need to be replaced wholesale with the ones from www.osoa.org.
Yours, Mike.
> sample composite files are invalid instance documents against SCA schema types
> ------------------------------------------------------------------------------
>
> Key: TUSCANY-1443
> URL: https://issues.apache.org/jira/browse/TUSCANY-1443
> Project: Tuscany
> Issue Type: Bug
> Environment: all
> Reporter: Michael Yoder
>
> The SCA samples composite files are invalid against the SCA schemas. In a
> component element, the property element has content. e.g. (from CppBigBank)
> <component name="AccountServiceComponent">
> .....
> <property name="currency">EURO</property>
> </component>
> When the XML Schema type does not allow mixed or simple content:
> <complexType name="PropertyType">
> <complexContent>
> <extension base="anyType">
> <attribute name="name" type="NCName" use="required" />
> <attribute name="type" type="QName" use="required" />
> <attribute name="many" type="boolean" default="false"
> use="optional" />
> <attribute name="override" type="sca:OverrideOptions"
> default="may" use="optional" />
> <anyAttribute namespace="##any" processContents="lax" />
> </extension>
> </complexContent>
> </complexType>
> The type is open to additional attributes, so the instance documents can be
> made valid with simple changes like this:
> <component name="AccountServiceComponent">
> .....
> <property name="currency" value="EURO"/>
> </component>
--
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]
