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: [email protected]
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]
