SOAP Resource Adaptor Changelog

Suppressed "Connection reset by peer" warning when clients request Connection: keep-alive but an intermediary e.g. a load balancer resets the TCP connection on idle. (HTTP-164)

All SLEE component versions have been updated to 2.3.

The resource adaptor now requires a valid license to activate in production Rhino instances. (SOAP-7)

The resource adaptor now supports HTTPS. (SOAP-30)

The HTTP transport layer used by the resource adaptor is now implemented using Netty. (SOAP-13)

Added support for active reconfiguration. Many configuration properties can now be updated while the RA entity is active. (See documentation for full list.) (SOAP-22)

Include the alarms raised by this resource adaptor in the runtime alarm catalogue. (SOAP-23)

The JavaBeans Activation Framework and SOAP with Attachments API for Java (SAAJ) are no longer included in the SOAP resource adaptor because they are part of the Java SE platform (since Java 6). (SOAP-14)

SBBs no longer require the java.lang.RuntimePermission "accessClassInPackage.com.sun.org.apache.xerces.internal.dom" security permission when using the SOAP resource adaptor. (SOAP-16)

In case of a SOAP error while processing the request, the HTTP response containing SOAP Fault now uses response code 500 (instead of 200). (SOAP-28)

Add permissions to the resource adaptor security policy and the example services to fix a problem loading SAAJ classes on more recent Java runtime environments. (SOAP-19)

The SOAP RA is now a separate download package and the Web Connectivity Pack has been deprecated.

Fixed a bug that resulted in the wrong activities being returned when multiple entities were being used. (SOAP-12)

Tracer names are no longer prefixed with "resource.<entity name>". (SOAP-8)

The packaging of the libraries and examples for the SOAP RA has been improved. (SOAP-9)

An alarm is now raised if no valid license is found when activating the SOAP RA. (SOAP-10)