On Wed, May 19, 2010 at 4:28 PM, Simon Nash <[email protected]> wrote: > Mike Edwards wrote: >> >> Luciano Resende wrote: >>> >>> I noticed that Eventing/PubSub spec has been released by OSOA [1], and >>> I was wondering what are the plans to get that implemented ? >>> >>> [1] >>> http://www.osoa.org/download/attachments/35/SCA_Assembly_Extensions_for_Event_Processing_and_PubSub_V1_0.pdf >>> >> Folks, >> >> First, the Event Processing & PubSub spec on OSOA, referenced above, has >> been out for some time. >> >> In the meantime, the spec has been submitted to OASIS and is now proposed >> as the major new item in the OASIS 1.2 SCA specifications. >> >> An initial version of the 1.2 specifcation, which includes the proposed >> Pub/Sub and Event Processing function, can be found here: >> >> >> >> http://www.oasis-open.org/committees/download.php/36508/sca-assembly-1.2-spec-wd01.doc >> >> http://www.oasis-open.org/committees/download.php/36508/sca-assembly-1.2-spec-wd01.doc >> >> There is active debate about the Event Processing function - Issue 227 has >> been under lively debate in the SCA Assembly TC for about a month: >> >> http://www.osoa.org/jira/browse/ASSEMBLY-227 >> >> http://www.oasis-open.org/committees/download.php/37273/sca-assembly-1.2-spec-wd01-issue-227.pdf >> >> Given that Tuscany SCA Java 2.x is about supporting the OASIS version of >> SCA, I suggest that our efforts should be directed at this version of the >> spec. I am happy to work on this with anyone. >> >> To kick things off: >> >> One significant piece of hassle in doing this is how to handle the >> extended XSDs - Event Processing adds >> >> o <producer/> and <consumer/> elements to componentType >> o <producer/> and <consumer/> elements to <component/> elements >> o <producer/>, <consumer/> and <channel/> elements to <composite/> >> >> and so on. >> >> Any ideas of how to do these extensions without being disruptive will be >> most appreciated. >> >> >> Yours, Mike. >> > Tuscany SCA Java 2.0 is currently targeted at supporting the OASIS 1.1 > version of the spec, which is fairly mature and stable. If we want to > support the event functionality at some stage, I would expect that to > happen in a future release of Tuscany. Depending on how disruptive the > event changes are, they might make it into the 2.x stream at some stage > or they might be part of Tuscany SCA Java 3.0. > > This suggests that we might need some other place in svn (a branch?) to > do initial investigations on adding the event functionality, so that it > doesn't impact mainstream 2.0 activity. > > Simon > >
We also want to think about how we handle compatibility and migration. What's the OASIS position on backward compatibility. For 1.x to 2.x we have two unrelated code bases because it covered the move from OSOA to OASIS. It would be nice to think that the addition of OASIS 1.2 functionality at some point in the future wouldn't be such a big jump but I expect it does mean a new XML namespace. Does it mean new/changed APIs? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
