Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

WSO2 ESB 5.0.0-BETA Released

Pre-release
Pre-release
Compare
Choose a tag to compare
@virajsenevirathne virajsenevirathne released this 20 May 20:02
· 297 commits to master since this release
v5.0.0-BETA
c4ba8d6

ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA Release. It contains following improvement and bug fixes.

Bug

  • [ESBJAVA-3117] - The bind-address feature was not implemented for Pass-through transport
  • [ESBJAVA-4137] - Empty POST body with application/json content-type throws an Error
  • [ESBJAVA-4225] - Endpoint re-deployment issue via a CAR while invoking the same endpoint
  • [ESBJAVA-4244] - JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input stream found.
  • [ESBJAVA-4297] - [ESB 4.9.0]Sample 57: Error when updating from admin UI.
  • [ESBJAVA-4326] - Overriding the Host Header in an HTTP Call from the ESB does not work with service chaining scenario
  • [ESBJAVA-4384] - Unable to use multiple mailto senders
  • [ESBJAVA-4387] - Mediation debugger failed to set breakpoints for Aggragete mediator inlined sequence.
  • [ESBJAVA-4401] - Product version and relevant details should be updated on distribution files for ESB 4.10 release
  • [ESBJAVA-4442] - [ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic Subscription
  • [ESBJAVA-4446] - [ESB500][JMS 2.0 Feature : JMSXDeliveryCount]Could not reconnect to JMS broker after loosing connection.
  • [ESBJAVA-4492] - Json to XML conversion is wrong when json attribute name has spaces
  • [ESBJAVA-4516] - publishing to DAS from scheduled task in ESB fails
  • [ESBJAVA-4533] - Cache mediator in cluster environment not working
  • [ESBJAVA-4536] - ESB continuously redeploy connector enabling files with backups
  • [ESBJAVA-4562] - WSO2 Call Mediator and Loadbalance Endpoints
  • [ESBJAVA-4564] - ClassCastException when aggregating SOAP Responses with SOAP Headers using Aggregate mediator in Secured Proxy
  • [ESBJAVA-4571] - "rabbitmq.channel.consumer.qos" parameter is not working as expected.
  • [ESBJAVA-4579] - Cannot update Inbound Endpoint definitions deployed via a CApp which contains registry resource references
  • [ESBJAVA-4590] - Script Mediator does not support concurrent execution and is using ScripEngine.eval() which does not guarantee state isolation between script executions.
  • [ESBJAVA-4591] - [WSO2 ESB Mediation Debugger][Clear Property] Clearing value of property give an error
  • [ESBJAVA-4601] - When creating an endpoint template and defining template endpoint with dynamic duration it fails
  • [ESBJAVA-4609] - Can not deployed more than one mqtt transport enabled proxy services
  • [ESBJAVA-4610] - MQTT proxy service can not send messages to another MQTT topic concurrently
  • [ESBJAVA-4611] - Cannot change the mediation flow and proceed by resending mediation flow break points
  • [ESBJAVA-4613] - JMS Proxy retrying fails in multiple proxies deployed setup when MQ restarted.
  • [ESBJAVA-4617] - Proxy source view shows as empty sometimes
  • [ESBJAVA-4625] - [ESB500][JMS] Logs show incorrect value

Improvement

  • [ESBJAVA-4060] - server_name support in client hello of TLS connection
  • [ESBJAVA-4328] - Encode REST_URL_POSTFIX
  • [ESBJAVA-4380] - Improve the script mediator allow set properties with a scope
  • [ESBJAVA-4411] - Upgrade Commons-net to 3.4
  • [ESBJAVA-4520] - Improve the Kafka Inbound performance
  • [ESBJAVA-4569] - RabbitMQ message store and message processor not support SSL
  • [ESBJAVA-4580] - xsi:type support in datamapper engine side

Patch

  • [ESBJAVA-4572] - "false" or "true" String values send as JSON, autoprimtives and autoprimtive disable regex has lower precedance
  • [ESBJAVA-4578] - enableMTOM property does not check in SynapseCallBackReceiver when Enabling MTOM

Task

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : dev@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature requests regarding WSO2 Enterprise Service Bus through the public JIRA. You can use the Carbon JIRA to report any issues related to the Carbon base framework or associated Carbon components.

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

To learn more about WSO2 Enterprise Service Bus and WSO2 support offerings please visit http://wso2.com/products/enterprise-service-bus/

-- The WSO2 Enterprise Service Bus Team --

Assets 3