Yes, the JAX-RPC and JAXWS should have common SAAJ impl. I don't think that JavaEE 5 spec mandate SAAJ 1.2 for JAX-RPC handlers. They must use common SAAJ 1.3 impl. The common SAAJ 1.3 impl for Axis 1 / Axis 2 will strike a great blow to Axis1 impl. (OM for Axis1 ? or Axis 1 restructuring)
If Geronimo adopt flexible architecture in JAX-RPC/JAX-WS impl (eg. Axis1/Axis2, Celtix, XFire, the SAAJ impl should go with the specific JAX-RPC/JAX-WS impl. -- Jongjin On 5/24/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Yes, you are right. we have a conflict and would need some classloader pixie dust for the SAAJ stuff. wonder how the GlassFish guys do it. Do they have 1 SAAJ Impl for both JAXRPC and JAXWS RI's? we need to poke more. Let me read the J2EE spec for a good measure and then comment. -- dims On 5/23/06, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: > > > Hi, > > I don't know enough about Axis1 to say with authority, but it seems like you might end up needing two different SAAJ implementations. JAX-WS requires SAAJ 1.3 so unless there is an effort to port that on to the Axis1 impl, then you might need two. That is, unless Axis1 can run without its own version SAAJ and on whatever version is included for JAX-WS instead. > > Regards, > > Nicholas Gallardo > WebSphere - WebServices Development > [EMAIL PROTECTED] > Phone: 512-838-1182 > Building: 901 / 5G-016 > > > > > David Blevins <[EMAIL PROTECTED]> > > > 05/23/2006 05:20 PM > > > Please respond to > axis-dev > > > > > To > axis-dev@ws.apache.org > > > cc > > > > Subject Re: [Axis2] Geronimo integration? > > > > > > > > > On May 23, 2006, at 2:57 PM, Rajith Attapattu wrote: > > > The JonAS guys also asked me the same questions about supporting > > both JAX-RPC and JAX-WS. > > Looks like their main concern is supporting existing users. > > > > Having Axis1 and 2 does seem to me like an ugly solution, but then > > JAX-RPC is a lot of work. > > Sometimes it's not worth it spending so much energy on something > > thats fading away. > > > > So ugly as it maybe we may have to go with axis 1&2 co-habitation > > route. > > I don't see any issues doing so (technically). Dims would have > > raised if there were class loading issues. > > Keeping them in different java packages is easy, but if the two drift > on the versions of third-party libraries they consume, that would be > a no-go. Fortunately, Axis 1 doesn't have too many thrid-party > dependencies. So who knows. > > > -David > > > > Regards, > > > > Rajith > > > > On 5/23/06, Tom Jordahl <[EMAIL PROTECTED]> wrote: > > I think you are going to need to support consuming rpc/encoded > > services. > > They aren't going to just go away.... > > > > Having Axis 1 & 2 in the same J2EE container seems like a fairly ugly > > thing to me. > > > > -- > > Tom Jordahl > > Adobe ColdFusion Team > > > > -----Original Message----- > > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 23, 2006 4:17 PM > > To: axis-dev@ws.apache.org > > Subject: Re: [Axis2] Geronimo integration? > > > > We don't want to do rpc/encoded in Axis2, JAX-WS does not mandate it, > > however JAX-RPC does need it and explicitly tests for it. So we would > > have to do both Axis1 (for JAXRPC) and Axis2 simultaneously. > > > > -- dims > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Davanum Srinivas : http://wso2.com/blogs/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
