About this Release

What is new in this release

WSO2 ESB version 5.0.0 is the successor of version 4.9.0, and it comes complete with the runtime, tooling, and analytics in a single release. 

WSO2 ESB 5.0.0 contains the following new features and enhancements:

• Tooling support provided via WSO2 ESB tooling to create and manage ESB artifacts.. For information on how to get started with WSO2 ESB tooling, see Installing WSO2 ESB Tooling.
• An analytics component to analyze WSO2 ESB mediation statistics. For information on WSO2 ESB analytics component, and how to analyze ESB mediation statistics via ESB analytics, see WSO2 ESB Analytics.
• JMS 2.0 specification support for existing JMS messaging features. WSO2 ESB supports the following new messaging features introduced with JMS 2.0:
  • Shared Topic Subscription. For a use case that demonstrates shared topic subscription with WSO2 ESB, see Shared Topic Subscription with WSO2 ESB.
  • JMSX Delivery Count. For a use case that demonstrates how WSO2 ESB can be used to detect repeatedly redelivered messages, see Detecting Repeatedly Redelivered Messages via WSO2 ESB Using the JMSXDeliveryCount Property.
  • JMS Message Delivery Delay. For a use case that demonstrates how you can use WSO2 ESB as a JMS producer and specify a delivery delay on messages, see Using WSO2 ESB as a JMS Producer and Specifying a Delivery Delay on Messages.
• WebSockets support via WSO2 ESB WebSocket Transport and WSO2 ESB WebSocket Inbound Protocol.
• Data Mapper Mediator.
• Mediation debugging capability to support message flow debugging at core ESB level. For information on how to debug the ESB message mediation flow, see Debugging Mediation.

What has changed in this release

This release includes a few features and functionalities that are deprecated and might be removed in a future release as well as some features and functionalities that are removed.

Deprecated features and functionalities

• The BAM mediator is deprecated and replaced by the Publish Event Mediator.

Removed features and functionalities

• The Axis2 Quality of Services UI to apply security policies, throttling and caching has been removed from the management console. For information on how to apply security, throttling and caching, see the following:
  • The recommended approach to apply security to a proxy service is via WSO2 ESB tooling. For instructions on the process of applying security to a proxy service, see Applying Security to a Proxy Service.
  • The recommended approach to enable throttling is to use the throttle mediator.
  • The recommended approach to enable caching is to use the cache mediator.

• The EHcache based implementation has been removed from ESB 4.9.0 and above due to distributed caching related issues with EHcache. We have moved onto a hazelcast based caching implementation with ESB 4.9.0 onwards, and officially support the hazelcast based caching implementation.

  Note

  The EHCache jar that was shipped with ESB 4.8.1 and older versions under the <ESB_HOME>/repository/components/plugins directory is not shipped with ESB 4.9.0. If you do want to use a third party jar like EHCache jar with ESB 4.9.0 and above, you can add the jar to the <ESB_HOME>/repository/components/lib directory.

Compatible WSO2 product versions

WSO2 ESB 5.0.0 is based on WSO2 Carbon 4.4.8 and is expected to be compatible with any WSO2 product that is based on the same Carbon version. If you come across any compatibility issues, contact team WSO2. For information on the third-party software required for running the ESB and its samples, see Installation Prerequisites.

Fixed issues

This release includes several bug fixes.

• For a complete list of issues fixed in the runtime of this release, see WSO2 ESB 5.0.0 - Fixed Issues.
• For a complete list of issues fixed in tooling of this release, see WSO2 ESB 5.0.0 Tooling - Fixed Issues.
• For a complete list of issues fixed in analytics of this release, see WSO2 ESB 5.0.0 Analytics - Fixed Issues.

Known issues

This release includes several known issues.

There is a known issue related to preserving CDATA blocks when you send CDATA inside a SOAP message payload. As a temporary workaround, you can add the XMLInputFactory.properties file with the following property to the <ESB_HOME> directory.

javax.xml.stream.isCoalescing=false

When you set this property to false, it can cause an issue in uploading CAR files from the Management Console. Therefore, if you need to upload a CAR file after adding the XMLInputFactory.properties file as specified above, you can either copy the CAR file directly to the <ESB_HOME>/repository/deployment/server/carbonapps directory or you can upload it via WSO2 Developer Studio 3.7.1 and later versions.

For a complete list of known issues in this release, see WSO2 ESB - Open Issues.