Compelling reasons to NOT USE axis yet: 1) Its is still alpha. Very alpha in terms of error handling. You if you expect always good SOAP, and don't mind AXIS dieing if someone is using "myPrefix25:string" instead of "xsd:string" for type names. 2) API will be similar 6 months down the road, but don't expect to just plug in new versions and go. You will need to update YOUR code, if you want Axis bug fixes.
Compelling reasons to USE axis now: 1) It does provide a lot of very nice features covering most common cases. 2) If you find that you would like Axis to have a feature that will make developing your services easier, it may actually get added to Axis, and make your life easier in the future. > -----Original Message----- > From: David Ethell [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 05, 2002 7:09 AM > To: [EMAIL PROTECTED] > Subject: Should we develop using Axis? > > > We are nearing the end of alpha development for a web services > application and have thus far used Apache Soap 2.2. The SOAP services > are working great, but now we'd like to add WSDL capabilities and also > look for general performance improvements. I've looked through the > axis-user list and it looks like either alpha-3 or the current CVS > snapshot is probably stable enough for our needs. We're not > pushing any > of the envelope with SOAP, just very typical RPC stuff with > nothing more > complex than Bean serialization for our objects. I'm leaning towards > moving from SOAP 2.2 to Axis using either alpha-3 or one of the latest > nightly builds. > > Is there a compelling reason not to do this? Our service > probably won't > be in production for another 6 months so I think the timing > seems right > to move to Axis now while we're still in development. > > Thoughts? > > Thanks much, > David Ethell >
