Hello Sanjiva, My previous message was not intended to anything that related to criticizing. My applogies if it did so.
I actually THANK YOU for you folks for the great contributions and I enjoy playing with your folks' artifacts. Otherwise, I wouldn't spend the time around here. I, as an individual in the user community, am only expressing on what would be more benefital and how we can create the better communities, including the dev. and user communities. Have a great day. Best, Pae > Hi Pae, > > I agree 100%; I am not going to decide how you and other users > will or will not migrate to Axis (or anything else). I wasn't > trying to; my apologies if it sounded like that. > > However, as Apache projects, Apache SOAP and Axis have a very > clearly defined relationship: Apache Axis is basically v3 of > a SOAP impl from Apache. As such *I*, as primarily a developer > of the V2 codebase (Apache SOAP codebase), don't intend to > continue to work on the Apache SOAP codebase when Axis is ready > for prime time (and past an alpha label). > > I am in no way stopping others from contributing to Apache SOAP. > If someone asks me, however, I normally suggest that they put > their energy towards Axis because that's the future direction. > > Sanjiva. > > ----- Original Message ----- > From: "Pae Choi" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, January 28, 2002 10:15 PM > Subject: Re: Apache Soap 2.2 questions > > > > One's understanding and vision of transition and progress in our > > history and nature does not necessarily reflect the "truth" of > > spontaneous phnomenon we had and we will continuously have. > > > > Do you really want to make a decision for the rest of world. Wouldn't > > it too much for you to make a such decision? Why don't you let the > > user community to decide for their own rights. It will not only make > > your life easier, but also create the smooth tansition. > > > > In addition, you wouldn't appreciate if someone else make a decision > > for your own life. Would you? Sometimes, understanding the scope of > > own roles and responsibilities indeed helps not only for own life, but > > alsofor the rest of world. > > > > > > Pae > > > > > > > > > > > > Axis made a strategic decision to support the emerging JAX RPC API's. > > JCP > > > > rules prevent Axis from being labeled final until this JSR is > complete. > > > > > > Ah, I hadn't realized this; my bad for not paying enough attention to > > > axis-dev. > > > > > > > Meanwhile, some big companies (take a wild guess which ones ;-)) are > > > basing > > > > their product plans on this codebase and investing heavily in it's > > > > development. There even has been a toolkit based on it released. > > > > > > Do you really feel that Axis is production ready? That was not > > > my understanding, but I'm (very) happy to be corrected!! > > > > > > > > If Axis does release a stable, migratable 1.0 within 3-6 > > > > > months then that will be the last release of Apache SOAP. > > > > > > > > There is no reason to preclude the possibility of releases of Apache > > SOAP > > > > 3, 6 or even 12 months *AFTER* Axis is released. > > > > > > Hypothetically, yes, but practically it makes no sense for Apache to > > > have two competing SOAP implementations. Axis had as a requirement > > > a good migration story for Apache SOAP users, so once that product > > > is indeed production ready, then its time for this SOAP implementation > > > to retire. If you recall that was exactly the conclusion that was > > > supported (by you too, if I recall correctly) in a recent discussion > > > on [EMAIL PROTECTED] > > > > > > I should say that this is my opinion only. If other committers feel > > > that it would make sense to keep Apache SOAP going then I will not > > > stand in their way. However, history doesn't indicate to me that that > > > situation is very likely. > > > > > > Sanjiva. > > > >
