> 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.
