axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: [Axis2] Moving SOAP classes to its own package
Date Fri, 13 May 2005 15:37:00 GMT
+1 to make it a maven module.

-- dims

On 5/13/05, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> On Fri, 2005-05-13 at 20:41 +0530, Venkat Reddy wrote:
> > The Axis 1.2 SAAJ stuff is in org.apache.axis.message package. Since
> > we don't have a "message" package in Axis2, no clash here, even if we
> > put these in org.apache.axis.om.soap.
> >
> > However, I'm +1 to keep these SOAP classes under
> > org.apache.axis2.om.soap package, because atleast it would tell people
> > that these are NOT a SAAJ implementation, but something specific to OM
> > and Axis2.
> 
> Yes the proposal is to make all of Axis2 be under o.a.axis2.
> 
> > BTW, Should we also move the SAAJ implementation to the main area for M2 ?u
> 
> As long as you create a new Maven module for it, +1.
> 
> I'm absolutely -1 to making SAAJ support be part of the Axis2 core. As
> we discussed in the F2F, Axis2 can be used in language on top of the
> JVM .. so it makes no sense to burn any Java language specific things
> (like JAX-RPC) into the core.
> 
> Also, are you guys following what's happening with JAX-WS vs. JAX-RPC
> etc.? Can you give an update please? I haven't had a chance to keep an
> eye on it ...
> 
> Thanks!
> 
> Sanjiva.
> 
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/

Mime
View raw message