Re: Move up to Axis2 1.3?
Axis2 1.3 has mentioned that this is a performance and bug fix update. Any axis2 user gets no infection to their code. Another point: At Tuscany side, any update of axis2 just affects inside Tuscany, user code is standard based. To those WS referenced by composites, they are interacted on bases of protocol(http, soap ). ant elder [EMAIL PROTECTED] wrote: On 8/14/07, ant elder wrote: Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant Actually, I've been talking to one of our big Tuscany users about this and it would be more convenient for them if we stayed at Axis2 1.2 for the time being so they don't have to update all their associated Axis2 code. ...ant - Need a vacation? Get great deals to amazing places on Yahoo! Travel.
Re: Move up to Axis2 1.3?
+1 to do this now. - Venkat On 8/14/07, ant elder [EMAIL PROTECTED] wrote: Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant
Re: Move up to Axis2 1.3?
On 8/14/07, ant elder [EMAIL PROTECTED] wrote: Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant Actually, I've been talking to one of our big Tuscany users about this and it would be more convenient for them if we stayed at Axis2 1.2 for the time being so they don't have to update all their associated Axis2 code. ...ant
Re: Move up to Axis2 1.3?
On 8/14/07, ant elder [EMAIL PROTECTED] wrote: Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant We will have to take your advice on whether it can be made to work this week. Assuming it can then +1 to sooner rather than later. The less we have to change just before 1.0 the better. Simon
Move up to Axis2 1.3?
Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant
Re: Move up to Axis2 1.3?
+1 to move to it now. We can also clean up the dependencies as Axis2 1.3 is now built with Maven2. Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Tuesday, August 14, 2007 6:33 AM Subject: Move up to Axis2 1.3? Axis2 1.3 has just been released so how about moving up to that? There's a lot of improvements and bug fixes in it and as its the level we'll likely go 1.0 with i think it would be good to get it in sooner so we have time to find and fixes any problems. There's a few minor changes we need to do in Tuscany to move up but I have it almost going, just one failing testcase remaining, so what do people think, should we move up now or wait till after our next release? ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
