Axis Change Log

Changes from 1.0 to 1.1

• Axis supports JMS for reliable messaging between client and server. Note that the actual wire format of JMS messages is vendor-specific at present, so you may not be able to use this to connect arbitrary JMS clients and servers without special bridging software. Refer to your particular JMS vendor for details. (rule-of-thumb is "if you can get a JMS connection working, we can talk SOAP over it." :))
• Many more WSDL and interop issues reported (thank you!) and fixed.
• Axis ant tasks are now documented, and are much enhanced.
• Axis now includes a Castor serializer, handing off XML marshalling to Castor. Castor integration offers schema validation and autogenerated Java classes from a Schema. Pending documentation and tests, this code is left for the experienced Castor user, who should look at the classes in org.apache.axis.encoding.ser.castor to discover what is available.
• Fixed a bug where clients running Java1.4 needed servlet.jar on their classpath
• Fixed a bug with Axis shutdown on Tomcat 3.3.1

Changes from 1.0beta-3 to 1.0

• 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 from 1.0beta-2 to 1.0beta-3

• Support for the new version of the DIME spec

Changes from 1.0alpha-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.