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. BTW, Should we also move the SAAJ implementation to the main area for M2 ? -- Venkat On 5/11/05, Simon Fell <[EMAIL PROTECTED]> wrote: > I'd be really really happy if the axis2 package/class names didn't clash > with the axis1.x names, so that I can run both axis1 & axis2 in the same > jvm instance. > > Cheers > Simon > > -----Original Message----- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 11, 2005 8:53 AM > To: [email protected] > Subject: Re: [Axis2] Moving SOAP classes to its own package > > +1 > > On 5/11/05, Glen Daniels <[EMAIL PROTECTED]> wrote: > > How about just org.apache.axis.soap? > > > > --Glen > > > > Eran Chinthaka wrote: > > > Hi, > > > > > > In the current source tree, all the SOAPXXXX classes are in the same > > > > package with OM classes. i.e org.apache.axis.om.*. > > > > > > Since SOAP classes are a specialization of OM and there are lots of > > > SOAP classes I propose to move all the SOAPXXX classes to > > > org.apache.axis.om.soap package. > > > > > > Comments and/or thoughts ?? > > > > > > -- Chinthaka > > > > > > > > > > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ > >
