Rather hopefully I evaluated the axis server only to find several bugs (showstoppers - encoding/concurrency) within a few hours of using it (beta 1). I did find it easier to use than SOAP 2.2, but SOAP 2.2 was more stable and that was what was required. The bugs didn't cause it to crash or anything obvious - it just corrupted the data!
Charlie [EMAIL PROTECTED] on 04/30/2002 10:16:52 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: Apche SOAP 2.2 or AXIS ???? Chad, chester, FWIW, this mirrors my experience _exactly_ timj > I started with Apache SOAP 2.2 initailly and got basic simple web service samples working. > Considered it's maturity, I was about to recommended my company to use it. Then I start to build MS client against. And I had a lot of trouble to get MS client (MS Toolkit 2.0 SP2, VB) to talk to Apache SOAP 2.2. -- This partially also due to I am kind of new to the SOAP Implementation (Even I have read a lot about it), partially due to the Apache SOAP encoding style is different from MS. May be there is someway to get around, but I was getting frustrated as I just want some demo to work. Then I started to play with axis, and found that interoperability point of view, AXIS is a lot easier. Chester This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates.
