I am not sure about moving up to Tuscany 2.0. Can anyone comment on the state of the 2.0 code to help me decide?
A few things come to mind: Have the specifications on which 2.0 is based even been finalized by OASIS? How stable is the code? There are many bugs in JIRA for 2.0, but much fewer for 1.6 - is it because 2.0 is in a state of flux, or because no one bothers with 1.6 anyway? What about the sad lack of documentation for 2.0? The very fine book "Tuscany SCA in Action" is based on 1.4 - how much of that will survive for 2.0? How much work would it be to migrate to 2.0 later on? What constructs should be avoided now to make such migration easier (conversational interfaces etc.)? When developing a business application, with a team that does not have much SCA experience, at the moment I'd feel slightly safer with 1.6. Do you think I should overcome that feeling? -- Sebastian > -----Original Message----- > From: ant elder [mailto:[email protected]] > Sent: Thursday, September 02, 2010 5:56 PM > To: [email protected] > Subject: Re: Q: Adding classes to a node > [snip] > > In the 2.x code there is an API that allows specifying an external > sca-contribution.xml file when installing a contribution, that enables > installing any arbitrary jar as a contribution and having an > sca-contribution.xml side file define which classes in that jar are > exported and so available to other contributions in the domain. Any > chance you can move up to the 2.x code? > > ...ant
