OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 175: Current Schema for Properties does not support value attribute - [ASM50027]


now logged:

http://www.osoa.org/jira/browse/ASSEMBLY-175


On Aug 11, 2009, at 5:24 AM, David Booz wrote:

> Since this issue has not yet been logged, I'd like to bundle a few  
> more problems (as discussed here [1] ) that are all related to  
> component properties. We should change the title of this issue IF we  
> decide to do this.
>
> In summary, from [1]:
> a) How should the content of a file containing property values be  
> used/parsed? As textural inclusion or XML inclusion?
> b) Clarify how the @file URI is resolved.
> c) Do we need to add extra ways of specifying values on <composite/>  
> <property/> elements (notably @file is not available on composite  
> properties)?
>
> [1] http://lists.oasis-open.org/archives/sca-assembly/200908/msg00075.html
>
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
>
> <graycol.gif>Luciano Resende---08/10/2009 10:27:07 AM---After we  
> updated to sca-core-1.1-cd04.xsd, some schema validation errors  
> related to properties star
>
> <ecblank.gif>
> From:
> <ecblank.gif>
> Luciano Resende/Westford/IBM@Lotus
> <ecblank.gif>
> To:
> <ecblank.gif>
> sca-assembly@lists.oasis-open.org
> <ecblank.gif>
> Date:
> <ecblank.gif>
> 08/10/2009 10:27 AM
> <ecblank.gif>
> Subject:
> <ecblank.gif>
> [sca-assembly] [NEW ISSUE] Current Schema for Properties does not  
> support value attribute - [ASM50027]
>
>
>
> After we updated to sca-core-1.1-cd04.xsd, some schema validation  
> errors related to properties started to happen as the one below
>
> XMLSchema validation error occured in: TestComposite50 .....  
> Attribute 'value' is not allowed to appear in element 'property'.
>
> The root cause of the issue seems to be the change from  
> <anyAttribute namespace="##any" processContents="lax"/> to  
> <anyAttribute namespace="##other" processContents="lax"/> on the  
> property complexType definition (see below). With this change, only  
> attributes from another namespace is allowed and thus the validation  
> complaints about the value attribute which is not defined.
>
> <complexType name="Property" mixed="true">
> <complexContent mixed="true">
> <extension base="sca:SCAPropertyBase">
> <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" use="optional"
> default="false"/>
> <attribute name="mustSupply" type="boolean" use="optional"
> default="false"/>
> <anyAttribute namespace="##other" processContents="lax"/>
> </extension>
> <!-- extension defines the place to hold default value -->
> <!-- an extension point ; attribute-based only -->
> </complexContent>
> </complexType>
>
>
> The value attribute should be defined.
>
>
>
> - Luciano
> Luciano Resende
> Open Source SOA - Apache Tuscany
> 4400 N 1st St, San Jose - CA
> notes: Luciano Resende/Westford/IBM
> internet IBM: luciano_resende@us.ibm.com
> internet ASF: lresende@apache.org
> Personal blog @ developerWorks : link
> Apache Tuscany blog: link
> Great things are not done by impulse but by a series of small things  
> brought together
> - Vincent Van Gogh
>
>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]