For a full list of ALL changes in CVS since 1.1RC2, click here.
The JAX-RPC specification of exceptions is now implemented; you may well be able to send abitrary exceptions over the wire and have them retranslated into Java Exceptions at the far end. Of course, non-Java destinations have a little problem there, all they get are the XML details to make sense of somehow. There is a lot to be said for creating, filling and throwing an AxisFault directly, and documenting the faultdetails elements for callers of all languages to make sense of. Axis now makes it easier to work with these details; consult at the AxisFault javadocs to see the new fault detail methods.
Axis no longer reports AxisFaults at INFO level on the client or server, unless you configure the logging parameters to do so; see the reference documents for details on how to do this. There is one exception: we do log server-side any AxisFaults created from RunTimeExceptions that are thrown by web service methods you implement. This is because those are usually bugs (like null pointer exceptions) that service developers like to know about before
For security reasons we have stopped sending stack traces over the wire to callers by default. The reference manual shows how to enable this on development systems.
Finally, we know we still have more to do to get exceptions fully under control. For example, global OnFault handlers are apparently not called consistently, and we need to do a lot more interop testing across platforms and languages. We also need a willing volunter to provide a guide to exceptions in SOAP and Axis.