I read Paul's document as well as the blog post. I think he makes a strong case. I am still ramping up on Axis so I can't comment(doesn't feel qualified to) on how well this concept can be embraced by Axis2.
But still paul's document convinces me that this maybe conceptually sound. If there is a clear separation of concerns I do believe that's a very strong point in any framework, and will make Axis more appealing to the user community. Besides Axis2 users can make full use of an IoC container if this route is taken. Something that will make Axis2 a natural choice if the application is for ex based on Spring. Strong Integration capability with complementing technologies is something very marketable, so in my opinion I think it's a right step towards the future. For ex: Pauls suggestion of allowing a choice in data binding solutions. If this is the route you guys are going to go then I will gladly jump in. I promised Sanjeewa I will help with documentation only (due to personal commitments), but Paul's proposal is just too tempting to be just content with documentation. Rajith. -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 10:07 AM To: [email protected] Subject: Re: [Axis2] Stub / Call Does JAX-WS impose any thread safety stuff on stub? if not i guess we don't have to. thanks, dims On 11/23/05, Glen Daniels <[EMAIL PROTECTED]> wrote: > Davanum Srinivas wrote: > > we'd have to see some proposals on how to modify the current code > > generation and runtime to implement that :) If we go this route, We > > also have another fundamental issue, same Stub instance is supposed to > > be usable across multiple threads. (First of all, we need to review > > the code and make sure that this is still true in current impl). We > > also need to figure out how to "inject the call" such that this > > premise still holds good. > > Who said the same Stub needs to be thread-safe? I don't think that's > true at all. We went through this in Axis1, and ended up deciding that > Stubs were per-thread after a long and problematic attempt to make them > sharable. I don't think we should put effort into making them thread-safe. > > --Glen > -- Davanum Srinivas : http://wso2.com/blogs/
