Axis 1.0 RC1 Release Notes
This is the RC1 release
of the Axis SOAP library.
Rationale for Releasing Axis 1.0
Many users have requested a v1.0 so that they can work from a relatively
stable base. Some users have even remained on Apache SOAP until v1.0 of
Axis is available. Now Axis has surpassed Apache SOAP in function,
performance, and interoperability and, in particular, has passed Sun's
JAX-RPC and SAAJ compliance tests, we decided to ship v1.0 as it
currently stands.
However, this is far from the end of the road for Axis. There is more
documentation to be written; the SOAP v1.2 spec. needs to be tracked to
completion and implemented fully; major functional enhancements and
architectural improvements are being considered. We particularly encourage
you to submit improvements to the documentation, however large or small and
in any format, to axis-dev@xml.apache.org.
The Axis Development Team
JAX-RPC
This release is intended to be 100% compliant with the
JAX-RPC and
SAAJ specifications from Sun.
The Axis code has successfully passed the all of the JAX-RPC and SAAJ
TCK (Technology Compatibility Kit) tests.
Why AXIS over SOAP 2.2?
The Axis code has:
- Significantly higher performance than Apache SOAP 2.2
- Good interoperability with other SOAP implementations
- A streaming-oriented model for message parsing (SAX, not DOM)
- A modular, configurable message handling architecture
- A pluggable transport framework
- Support for WSDL generation and code generation from WSDL
- An extensive package and functional test suite
What's New?
Changes since beta-3
- Axis now passes the JAX-RPC and SAAJ TCK test suites.
- Many bugs have been fixed.
- Axis now supports (almost) all XML Schema types in WSDL
- Some basic performance tuning has been done
- Attachments are now supported in WSDL2Java
Changes since beta-2:
- Support for the new version of the DIME spec
Changes since alpha-3:
- Closer to JAX-RPC compliance.
- Support for SOAP Messages with Attachments.
- Much better XML schema type support.
- Document/literal support.
- Now using the org.apache.commons.logging APIs as a common logging interface.
- Many minor bug fixes.
Please check out the included documentation and the FAQ for more information.