WSO2 Web Services Application Server(WSO2 WSAS) 2.1 Release Notes

10th October 2007

WSO2 WSAS is the Enterprise ready Web services engine powered by Apache Axis2. It is lightweight application server for Web services that incorporates leading open source components into a simple, easy-to-use and highly performant package.

It supports Java components as services using both SOAP and REST models. Web services support include WS-Security, WS-Trust, WS-SecureConversation, WS-Reliable Messaging, WS-Addressing, WS-Policy, WS-SecurityPolicy and more, giving a full secure and reliable infrastructure that interoperates with both J2EE and .NET frameworks using open standard protocols.

WSO2 WSAS is built on Apache Axis2, the popular Web services framework mainly developed by WSO2 engineers. WSO2 WSAS provides many value additions on top of Axis2, making it a more enterprise ready product. It integrates other core Apache Web services projects such as Apache Axiom, Apache Rampart, Apache Sandesha2 , and Apache Neethi to form a production quality, comprehensive Web services server platform.

An open source product, WSO2 WSAS is available under the Apache Software License (v2.0). This includes all of the extra integration and management functionalities as well.

WSO2 WSAS can be used as a standalone server or within a J2EE compliant servlet container. It also contains client components required to communicate with services. The support for WS-ReliableMessaging and WS-Security means that WSO2 WSAS is ideal for hosting B2B solutions, or building enterprise class integrated applications.

New Features In This Release

WS-* Support

Open Source components included in WSO2 WSAS/Java

Tools

Apache Axis2 modules included with WSO2 WSAS

Known Issues

  1. POJO to Web service feature is still at an experimental stage. One can upload jar/zip file and can create an AAR out of it. If you uploaded a jar/zip file which has the semantics of an AAR, when its transformed into AAR its services.xml will be replaced by the generated services.xml. In addition to this, the user cannot give associate any library dependencies or web content with the generated AAR file.
  2. WS-Policy support is still in the experimental stage and limited to single port scenarios.
  3. You cannot have two different versions of the Apache Sandesha2 module in the system.
  4. A <parameter name="OmitSOAP12Action">true</parameter> entry has been added to the HTTP & HTTPS transportSenders in order to overcome some issues with some browsers. In case of interoperability failures, please change the value of this parameter to false and retry.
  5. The 'Try It' feature does not work for MTOM enabled services.
  6. Persistent Reliable Messaging support is experimental. Thus it might not provide QoS expected, during every possible interruption scenario..
  7. When daemon.sh is used in Gentoo kernel that runs on Intel processors with 32/64 bit, users probably have to rename the native binaries with the proper name as given in error message.

Reporting Problems



Issues can be reported using the public JIRA available at https://wso2.org/jira/browse/WSAS

Contact us

WSO2 WSAS developers can be contacted via mailing lists:

For Users: wsas-java-user@wso2.org

For Developers:wsas-java-dev@wso2.org

For details on subscriptions see http://www.wso2.org/projects/wsas/java#mail



Alternatively, questions can also be raised in the forums:

For Users: http://www.wso2.org/forum/181

For Developers: http://www.wso2.org/forum/184

For more information on WSO2 WSAS, visit the WSO2 Oxygen Tank

Thank you for your interest in WSO2 WSAS

-The WSO2 WSAS Development Team