Support for JDK 1.6
Fix for the XML signature HMAC truncation authentication bypass security hole (See this to learn about the HMAC length truncation security hole).
MTOM/XOP
messages resent by WS-RM now use MTOM optimization if possible,
validation fully works with MTOM,
xop:Include is resolved in the message parts deserialized as org.w3c.dom.Node,
new per-call properties org.systinet.wasp.webservice.CallContext.MTOM_MAX_ATTACHMENT_PARTS and MTOM_ATTACHMENT_SIZE_TRESHOLD were introduced,
HTTP proxy settings are runtime re-configurable and also supports address ranges,
memory leak in the repeated deploy/undeploy part of service was fixed,
fixed the bug with wrong composition of ref and min/maxOccurs.
Support for Oracle 10g Applicaton Server has been added.
JVM property -Dlog4j.modify.relative.paths affecting backward compatibility was added (See System Properties).
Generation of JMS correlation IDs was changed. Now, they are always 32 bytes long.
Since this version the SSJ Governor supports REST communication with Policy Manager 2.0. Thus, the backward compatibility with Policy Manager 1.0 is violated because the GET command used in previous versions is not supported at all.
Deserialization of anyType instances without xsi:type mapping is supported now. See Handling of anyType for details.
The wsdl2java tool has new properties --mixed-to-dom (see Handling of mixed content) and --target-java (see Command-Line Options).
To improve interoperatibility, MTOM implementation supports now the always-including-faults option for server configuration and for per call context. See MTOM Settings and Runtime Configuration
SSJ Governor supports Systinet Registry 6.5.
Fixed issues with context class loader. Its usage is documented in the Context Class Loader chapter of Developer's Guide/Writing web services.
WS-Security
WSO2 SOA Enablement Server for Java now supports OASIS WS-Security 1.0 Errata 1.0
WSO2 SOA Enablement Server for Java now supports references to an X.509 security token by Issuer and Serial Number
WSO2 SOA Enablement Server for Java now supports custom tokens other than BinarySecurityToken
Performance improvements
Full support for WS-I Attachments Profile 1.0 WSO2 SOA Enablement Server for Java 6.5 fully supports WS-I Attachment Profile 1.0 in its default setting.
MTOM/XOP support MTOM/XOP optimization is supported for both SOAP 1.1 and 1.2 including combination with WS-Security.
WS-ReliableMessaging upgrade WSO2 SOA Enablement Server for Java 6.5 supports the February 2005 WS-ReliableMessaging Protocol. This feature is a technical preview.
Governing of Web services WSO2 SOA Enablement Server for Java 6.5 supports runtime governance of Web services using the Systinet Registry extension. This feature is a technical preview.
WS-I Basic Profile 1.1 Compliance WSO2 SOA Enablement Server for Java is now compliant with WS-I BP 1.1 (subject to the caveat described in Known Issues).
Support of Thread Pooling in JMS Transport To ensure the scalability and robustness of the server, WSO2 SOA Enablement Server for Java's JMS transport now uses the same pooling technique as its HTTP transport. The number of concurrent threads is now limited while the processing of concurrently arriving messages is speeded.
WS-ReliableMessaging enabled over server clusters Servers that are load balanced with CISCO LocalDirector are now WS-RM enabled. Integrity of reliable delivery is assured for WSO2 SOA Enablement Server for Java deployed to a cluster.
UDDI Version 3 supported In all cases where WSO2 SOA Enablement Server for Java uses UDDI integration or supports UDDI access, it offers usage of both UDDI V2 and V3.
JDK 1.5 supported Sun JDK 1.5 is supported on Windows, UNIX and Solaris platforms.
IBM AIX 5.3 supported IBM AIX 5.3 with IBM JDK 1.4 is supported.
JBoss 4.0 supported WSO2 SOA Enablement Server for Java may now be ported to the JBoss 4.0 application server/JMS provider.
Encrypted passwords in LDAP UserStore LDAP UserStore now supports SHA, SSHA, CRYPT, MD5 and SMD5 password digests, as well as plain passwords.