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: Re: [sca-assembly] Extensibility of current Assembly Schema



Luciano,

I don't know whether you want to raise a formal issue on this topic - your note is not marked "new issue" so
I can't treat it as such.

I will put it on the agenda for today's call as a discussion item - it would be great if you could join the call.


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com



From: "Luciano Resende" <luciano_resende@us.ibm.com>
To: sca-assembly@lists.oasis-open.org
Cc: "Luciano Resende" <luciano_resende@us.ibm.com>, "Raymond Feng" <rfeng@us.ibm.com>
Date: 04/02/2010 19:17
Subject: [sca-assembly] Extensibility of current Assembly Schema





In Apache Tuscany, we make heavy usage of the extensibility capabilities of the SCA Schema to create new implementation/bindings or extend existent ones. While trying to move our current implementation to the latest schema drafts, we have started to hit various issues similar to the one described in ASSEMBLY-177.
]]


- The CompoentType definition needs to remove the XSD any declaration
- The Callback definition needs to remove the XSD any declaration
- There are issues trying to define new WireFormats and OperationSelectors and we might need to add similar approach from ASSEMBLY-177 to accommodate this.


In summary, there is a urgent need to review all the extensibility plug points for the current schema. After discussing with Raymond Feng, we suggest that all the places that have both <any> and substitutionGroup be reviewed, including <implementation>, <binding>, <wireFormat>, <operationSelector> and we could probably re-open Issue 177 to track this problem.


Also, to avoid these type of issues in the future, I'd like to suggest that creation of some dummy schemas that extend the SCA ones utilizing a different namespace to proactively catch these issues.


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

- 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










Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU








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