I'm not sure we can give you a yes or no answer on that, it depends, and you'll need to decide for yourself. Some things to consider could be:
- as its a milestone release APIs may change on the way to 2.0 final, so when you need to move up to later milestones or the 2.0 final release you may need to update your code for the changed APIs. - compared to 1.x there are so far only a limited set of extensions for binding protocols and implementation types. If M2 has what you need then that may not matter. - we've done no performance tuning - as 2.x is all new and shiny its more fun to work on so when you send emails to the Tuscany dev or user lists, or raise JIRAs, or need fixes, then you may get more people helping you than if it was for 1.x. HTH, ...ant On Tue, May 26, 2009 at 7:44 AM, Chaula Ganatra <[email protected]> wrote: > > > Hi, > > Please suggest, can we go ahead with tuscany-sca-2.0-M2 for production > environment? > Our application would be deployed in jboss 4.0.2. > > Regards, > Chaula > ________________________________ > From: [email protected] > To: [email protected]; [email protected] > Subject: tuscany-sca-2.0-M2 for production environment > Date: Mon, 25 May 2009 10:55:13 +0530 > > Hi, > > Please suggest, can we go ahead with tuscany-sca-2.0-M2 for production > environment? > Our application would be deployed in jboss 4.0.2. > > Regards, > Chaula > > ________________________________ > Get easy photo sharing with Windows Live™ Photos. Drag n’ drop > ________________________________ > MSN Quiz Test your skill and wits on this revered battleground of knowledge > IMing with Windows Live Messenger just got better.
