Thursday, November 18, 2010

Axis2 1.5.3 released

The Apache Axis2 team is pleased to announce the general availability
of the Axis2 1.5.3 release.

1.5.3 is a maintenance release that contains the following improvements:

* Improved support for SSL when using the servlet transport: Axis2 can
now be configured so that generated WSDLs contain https endpoints
(AXIS2-4465).
* Improved compatibility with Rampart (AXIS2-3213 and AXIS2-4870) and
Sandesha2 (potential HTTP connection pool starvation).
* Axiom has been upgraded to 1.2.10. This version contains performance
improvements relevant for Rampart.
* Application (business) faults are no longer logged at level ERROR
(AXIS2-4280).
* Improved conformance to the SAAJ specifications. The 1.5.3 release
contains a set of fixes and improvements for the SAAJ implementation
developed on the trunk and not included in previous releases from the
1.5 branch.
* Axis2 now relies exclusively on dependencies available from the
Maven central repository, and no other Maven repositories are
required. This in particular fixes a build problem that appeared after
the 1.5.2 release.
* The Eclipse and IntelliJ IDEA plugins are again available for
download via the Axis2 Web site (previous 1.5.x versions could only be
downloaded from the Maven repository).

The complete list of JIRA issues fixed in this maintenance release can
be found here:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10611&fixfor=12315367

The new version is available for download at the following location:

http://axis.apache.org/axis2/java/core/

Please report any issues via JIRA: http://issues.apache.org/jira/browse/AXIS2.

As always, we welcome any and all feedback at:

java-dev@axis.apache.org - for developer-related questions/concerns
java-user@axis.apache.org - for general questions, usage, etc.

Thanks for your interest in Apache Axis2!

-- The Apache Axis2 team

1 comment:

Peddi said...

we were having issue "ADD_MUST_UNDERSTAND_TO_ADDRESSING_HEADERS". We are using Axis2 version 1.4.1. we can see an attribute named soapenv:mustUnderstand="0" is added to header. Though the value is "0"(which means can be omitted) it can be ignored by the requestprovider. They are nacking the and not going to fix. They were asking us to fix. I can see the same issue in the forums(AXIS2-3982), was curious to know if its resolved as part of 1.5 or still an open issue. can you please let us know