Folks,
This is a screw-up in the online versions of the XSDs on www.osoa.org -
they don't match the spec declarations for the XSDs.
I'll go fix that, since those online files have no business failing to
match the spec.
Yours, Mike.
Jean-Sebastien Delfino wrote:
Matthew Peters wrote:
p. 26 of the 1.00 Assembly Spec describes a mustSupply attribute on a
<property> inside a <composite>, used to mean that there is no default
value and a value must be supplied by the component that uses the
implementation. I don't see this attribute in the sca-core.xsd from
the 1.0 Tuscany or any discussion of it on the mailing lists. Has the
attribute gone for good, and has the concept gone as well?
I am assuming that the noDefault attribute (used to be "required") is
for use just within a component type but perhaps that's wrong.
Matthew Peters
The mustSupply attribute described in the assembly spec is implemented
by the Tuscany assembly model, XML readers and writers.
The SCA XSD says:
<attribute name="noDefault" type="boolean" default="false" use="optional"/>
instead of
<attribute name="mustSupply" type="boolean" default="false"
use="optional"/>
IMO this is a bug in the XSD, I'll report the issue to the OASIS
assembly TC.
In the meantime, you can try to specify that mustSupply attribute
anyway. It should work in Tuscany and XMLSchema validation shouldn't
complain about it as the XSD for <property> allows for <anyAttribute
namespace="##any" processContents="lax"/>.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
