Hi Dan, Wow. Damning criticism.
> I don't doubt that the Axis2 developers are working very hard to get > all these issues resolved, but for goodness sake...you can't release a > product as version 1.0--which implies a non-Beta, stable release--when > the new product lacks much of the basic functionality that people are > going to need and that they are used to having provided for them by > the previous release (Axis 1.x). First of all, sorry for the bad taste Axis2 has left in you. That was obviously not our intent. However, you touched the part of Axis2 1.0 which was done last and hence was least tested: RPC support. Yeah I know its easier to write Java classes and make them into services automagically but Axis2 was designed for a much more XML centric world. It can of course do the RPC style easily too but its fundamentally designed for a WSDL 2.0 like XML centric world where RPC is one pattern and a good bit of the time application authors deal directly with XML. 1.0 was really a release that made the XML case work and had relatively little put into making the RPC case work well. In retrospect, assuming that people will fiddle around with XML was a mistake. Hindsight is always 20/20. OTOH, until 1.0 was released it was impossible to get strong user engagement. Its a chicken-n-egg problem too. Furthermore, as a few others have stated already, this is a total rewrite of the Axis project and not a tweak. That was necessary for lots of reasons. As a rewrite it will take some time to go thru the growing pains. I hope you will try 1.1 .. that should be much more stable. In particular, it would greatly help if you could try the release candidates as they come out over the next week so that we can make sure everything is caught and fixed properly in 1.1. Thanks, Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
