WSO2 Enterprise Service Bus (ESB), v 1.5 Release Note

November 12th, 2007 - WSO2 ESB, v1.5 Released!

WSO2 ESB is a lightweight, and high performance Enterprise Service Bus (ESB). Based on Apache Synapse and Apache Axis2 projects, it supports connectivity, transformation, mediation and the management of Web services interactions.

WSO2 ESB is released under the Apache License v2.0

New Features

WSO2 ESB 1.5 Features

• Apache VFS based file transport
• Scheduled Task support
• New mediators - XQuery, POJO Command, DB Report and DB Lookup
• New EIP mediators - Split/Clone and aggregator mediators
• Cache, Throttle and Class mediator enhancements
• Improved logging and tracing support, and reconfiguration of Log4J instance at runtime
• Ability to save/edit sequences and endpoints directly to/from the integrated registry
• Ability define more than one administration account
• General UI usability enhancements and fixes

WSO2 ESB 1.0 Features

• Proxy services - facilitating transport, interface (WSDL/Schema/Policy), message format (SOAP/POX), QoS (WS-Security/RM), and optimization switching (MTOM/SwA)
• Non-blocking HTTP/HTTPS transport for ultrafast execution and support for many connections.
• Integrated Registry/Repository, facilitating dynamic updating and reloading of the configuration and resources.
• Easily extended via custom Java class/Spring mediators, or BSF Scripting languages (JavaScript, Ruby, etc)
• Load-balancing/Fail-over and Throttling support
• WS-Security, WS-Reliable Messaging, and Throttling configurable via WS-Policies.
• JMS message support for binary, plain text, and XML payloads.
• Facilitates easy management and monitoring of the service infrastructure.
• Lightweight, XML, Web services centric message model.
• Configurations serialized into a file system for versioning/backup and restoration.

Known Issues and Limitations

1. WSO2 ESB known issues and limitations deffered for the next release

ESBJAVA-309 - Unable to view/edit the sequences after clicking on the "Close" icon of the WSO2 ESB Sequence Editor window of a sequence in the Integrated Registry

ESBJAVA-308 - Incorrect information logged when executing a configuration which has a reference to a sequence which is exported into the Integrated Registry

ESBJAVA-304 - No options provided to select onReject and onAccept Sequences as reference keys when creating a sequence with the throttle mediator

ESBJAVA-270 - Unable to load the ESB Management console if JMS is enabled and the JMS server is not started

ESBJAVA-268 - Unable to start the axis2server.bat on Windows

ESBJAVA-258 - ESB hangs during startup if the actual service that a Proxy Service (created using a WSDL Endpoint) points to is down.

ESBJAVA-315 - The cache mediator does not function properly when configuration is created through Administration Console

The Aggregator mediator currently does not have a configuration UI with this release of the ESB

2. As the WSO2 ESB 1.5 depends on the Apache Synapse 1.1, it inherits the list of known issues of the Apache Synapse 1.1 release listed below

SYNAPSE-174 - The non-blocking http/s transports cannot handle WS-RM requests

- Caused by the NIO http/s transport being out of synch with the latest Sandesh2 codebase

SYNAPSE-170 - VFS transport listener sample - In the response sent via email, all tags define the same namespace

- Caused by an Axis2 Mail transport limitation

SYNAPSE-161 - Can't persuade Rampart to send certificate serial + issuer - only either BinaryToken or Identity

- Issue related to Apache Rampart

SYNAPSE-103 - WS-RM not returning response message

- related to SYNAPSE-174

The Synapse JMS implementation supports JMS 1.0.2b, however due to licensing issues we include the JMS 1.1 spec JAR from Apache Geronimo (geronimo-jms_1.1_spec-1.1.jar) instead. If you have any issues with JMS 1.0.x, please download the Sun JMS 1.0.2b JAR and replace supplied JAR from Geronimo.

You may encounter a "java.net.UnknownHostException: java.sun.com" while starting the WSO2 ESB without a connection to the Internet. This is caused by the bundled Spring JAR file. If you will not be using the Spring mediator, you may remove this file from the lib directory.

3. Dependencies are currently allowed to be removed while live references exists

The ESB UI currently does not perform a check on references before the elements are allowed to be removed. Thus there is a possibility of defining references to non-existent endpoints, sequences etc. as well as removing them while live references still exist.

Frequently Asked Questions

1. If you get an error related to WS-Security or when using it, check to ensure that your JDK uses the "Unlimited Strength Jurisdiction Policy Files". These could be downloaded from http://java.sun.com/javase/downloads/index_jdk5.jsp Refer to the associated documentation for instructions on how to install it to your JDK.
2. If you encounter issues with your JDK related to XML processing, try placing the Xerces jar files xercesImpl-2.8.0.jar and xml-apis-1.3.03.jar in your <JDK>/jre/lib/endorsed/ directory.

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

• Developer List : esb-java-dev@wso2.org | Subscribe | Unsubscribe | Mail Archive
• User List : esb-java-user@wso2.org | Subscribe | Unsubscribe | Mail Archive

Reporting Issues

WSO2 encourages you to report issues and your enhancement requests for the WSO2 ESB using the public JIRA.

You can also watch how they are resolved, and comment on the progress..

Discussion Forums

Alternatively, questions could be raised using the forums available.

WSO2 ESB Forum : Discussion forum for WSO2 ESB developers/users

Thanks,

-WSO2 ESB Team