Welcome to WSO2 Enterprise Service Bus (ESB) v1.6
January, 2008 - WSO2 ESB, v1.6 Released!
[Download] | [Documentation Index] | [Project Resources]
| [Official Web site]
The WSO2 ESB is an ultra fast, light-weight and versatile Enterprise Service Bus
based on the Apache Synapse ESB. It allows you
to Connect, Manage and Transform service interactions between Web services,
REST/POX services and Legacy systems
WSO2 ESB is released under the Apache License v2.0
New Features
WSO2 ESB 1.6 Features
-
Ability to pin a proxy or a task to server instances
-
Improved error handling in JMS transport
-
New Mail transport that supports POP3/IMAP/SMTP
-
Clustering support for the Cache/Throttle mediators
-
Maintainance mode support for the HTTP transport
-
JMX statistics monitoring and management support
-
New mediator - Callout
-
Improved REST/POX support
-
Annotations support for POJOCommand mediator
-
Ability to edit UI-less mediators in raw XML
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
- WSO2 ESB known issues and limitations
- ESBJAVA-234 - After clicking on the "Close" button of the "Sequence Editor" window when adding
anonymous sequences to a Proxy Service, the mediators lost the next time you open the "Sequence
Editor" window
- ESBJAVA-351 - The average response time of "Server Statics" displayed as NaN under some instances
- ESBJAVA-268 - Unable to start the sample axis2server.bat on Windows
- ESBJAVA-373 - [IE] When the wso2-esb.log is about 2MB and when trying to access System logs using
IE, the browser hangs and the CPU usage goes upto about 50%
- 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-408 - Support improved renaming of files in VFS transport
- As the WSO2 ESB 1.6 depends on the Apache Synapse 1.1.1, it inherits the list of known issues of
the Apache Synapse 1.1.1 release listed below
- SYNAPSE-180 - Require the ability to throttle by concurrency within a cluster
- SYNAPSE-174 - The non-blocking http/s transports cannot handle WS-RM requests
- SYNAPSE-213 - Improve handling of input in XSLTMediator
- SYNAPSE-211 - Improve performance in XSLTMediator when temporary files are used
- SYNAPSE-212 - XSLTMediator doesn't close/delete temporary files properly
- 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.
- Dependencies are currently allowed to be removed from the admin console, while live references
remains
- 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.
How You Can Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
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