On Thu, Sep 2, 2010 at 3:39 PM, Millies, Sebastian <[email protected]> wrote: > 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? >
You should definitely move to 2.x, and in the case that you might be using some extensions not yet migrated to 2.x let us know, or let us migrate it. > 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? 2.x has been in more active development, and we are also tracking compliance fixes/todos via jira, that's probably why. > What about the sad lack of documentation for 2.0? A lot of 1.x documentation still applies to 2.x. We have also started a wiki to migrate 2.x specific documentation at http://tuscany.apache.org/documentation-2x/ > 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.)? > A lot of the concepts haven't changed, samples might change a little, but people have started porting the Travel Sample to 2.x as well, which is the sample used in the book. > 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? > Yes, and if you find issues, you will definitely get a quicker fix if this is in the 2.x code stream. Well, these are my personal view.. others feel free to jump with your thoughts. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
