# WSO2 Web Services Application Server(WSO2 WSAS) 2.1-RC6 Release Notes

### July 23rd, 2007

WSO2 WSAS is a 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. It integrates other core Apache Web services projects such as Apache Axiom, Apache Rampart, Apache Sandesha2 ,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

- Data services support
- Eclipse IDE integration
- Clustering support
- Full support for WS-Security, WS-Trust, WS-Policy and WS-Secure Conversation and XKMS
- EJB service provider support
- Axis1 backward compatibility

## WS-* Support

- SOAP 1.1/1.2
- WSDL 1.1
- WSDL 2.0
- MTOM, XOP & SOAP with Attachments
- WS-Addressing
- WS-Security
- WS-Trust
- WS-SecureConversation
- WS-MetaDataExchange
- WS-SecurityPolicy
- WS-ReliableMessaging
- WS-Policy
- WS-PolicyAttachment
- WS-MetadataExchange
- WS-Transfer

## Open Source components included in WSO2 WSAS/Java

- Apache Axis2 (SOAP)
- Apache Axiom (High performance XML Object Model)
- Apache Rampart/Apache WSS4J (WS-Security)
- Apache Rahas(WS-SecureConversation)
- Apache Sandesha2 (WS-ReliableMessaging)
- WS-Addressing implementation in Axis2
- Apache Neethi (WS-Policy)
- WS-SecurityPolicy implementation in Axis2
- Apache XML Schema
- Apache Derby (Database)
- Hibernate (Persistence)
- Embedded Apache Tomcat
- Apache Tribes (Group Communications Framework)

## Tools

- AJAX based Management Console with complete administration capability of the server
- Command line system administration tool
- WS-Commons TCPMon
- WSDL2Java and Java2WSDL tools
- IDE Integration

### Apache Axis2 modules included with WSO2 WSAS

- Apache Rampart: Supporting WS-Security & WS-Trust
- Apache Rahas: Supporting WS-SecureConversation
- Apache Sandesha2: Supporting WS-Reliable Messaging
- Mex: Supporting WS-MetaDataExchange
- Throttle: For throttling requests
- Statistics: For gathering & monitoring statistics
- Tracer: For tracing SOAP requests & responses
- WSO2 WSAS Administration: For administering Web services
- XFer: Supporting WS-Transfer

## 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.
   - Due to limitations in Axis2, method overloading is not supported, and hence the WSDL for services where methods are overloaded cannot be generated. Hence all WSDL based functionality related to services will not work.
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.

## 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

© 2007 WSO2 Inc.