Hi Simon,
The OASIA SCA specification does not provide any "binary" backwards compatibility with OSOA code. This means that all OSOA code would need to be updated to work with an OASIS Open SCA runtime. The way that I see it working is that OSOA code would be supported on Tuscany 1.x releases and OASIS Open code would be supported on the Tuscany 2.x releases. Ideally, at some point in the future, we would provide some tooling support along with Tuscany 2.x that would help developers convert 1.x applications to 2.x applications. Currently, I feel that adding support for both the OSOA and OASIS Open applications to the 2.x codebase would add considerable complexity so I would prefer not to do it at this time. Thanks, Mark _____ From: Simon Laws [mailto:[email protected]] Sent: 26 January 2009 10:38 To: [email protected]; [email protected] Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790 On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack <[email protected]> wrote: Hi, Recently, the OASIS SCA-J committee agreed to change the package name from org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been raised as TUSCANY-2790. I would like to start working on changing the package name to org.oasisopen.sca on the 2.x root. However, I realise that this could be a rather disruptive change especially if we are planning to release M1. How do people feel about me attempting this change later this week or early next? Thanks, Mark [1] https://issues.apache.org/jira/browse/TUSCANY-2790 Hi Mark Is the proposal to change what is there or to add a new modules alongside what is there with the new package names. To ask the question another way. Do we expect that 2.x will support 1.x compatible applications also. It would be very nice if backward compatibility were provided but it adds complexity. Simon
