Apache
SOAP is based on the original SOAP4J code base that IBM contributed to Apache in
April 2000. This implementation isn't WSDL-aware. It requires that you include
type information on the wire (in the SOAP messages). It has interoperability
issues. It has a proprietary API. It has limited extensibility features. It has
very slow performance.
About 20 months ago, rather than try to rework the old Apache SOAP
code base to resolve thes problems, the Apache SOAP engineering team decided
that it would be easier to start over from scratch and design a new SOAP
implementation with a more flexible and extensible architecture. So they started
the Apache Axis project. Since then very little work has been done on the Apache
SOAP code base (mostly just bug fixes), and almost all efforts have been focused
on Axis. Apache Axis is a second generation SOAP implementation. It's fully
WSDL-aware. It supports the JAX-RPC API. It offers better performance than
Apache SOAP. It's designed to be extensible -- it's easy to use alternate
transports (e.g., SMTP, JMS, etc), it's easy to support complex types, headers,
etc. It's interoperable. And it has much better tools than Apache SOAP. Apache
Axis is still in beta, though.
Anne
-----Original Message-----
From: Mark Hansen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 19, 2002 6:23 PM
To: [EMAIL PROTECTED]
Subject: Axis vs. Apache SOAPWhat is the difference between Axis and Apache SOAP?
