Mule 0.9.2 Release Notes
There is a whole load of new goodies in this release, including Spring events integration, a new Servlet provider, a powerful mule client, improved routing support, groovy transformer support and more. Not to mention a lot of bug fixes and improvements.
The mule manager can now server as a Spring event broker. Spring beans can send and receive Mule events over jms, smtp, pop3, http or any other mule transport using the Spring events api. Read more…
Is a new provider for sending and receiving events via servlets. There is also a servlet implementation that uses the Servlet provider to enable REST style services access.
The Mule Client is a simple but powerful client for communicating with a mule server. It allows any client such as Jsp, scripting or plain old java to send and receive events through a Mule server.
Routing has been improved adding standard inbound and outbound router implementations such as -
Selective Consumer - Filter based message consumption
Idempotent Receiver - ensure every message received is unique
Content-based Router - route message based on it’s content using filters.
Message Splitter - Routing message parts to different recipients
Recipient List - Routing the same message to multiple recipients
Broadcast Router - Routing the same message over multiple transports
Of course, it is very easy to implement your own.
Simplified Mule configuration using Springs auto wire functionality. Read more…
Event chaining from synchronous calls are now propagated across Jms servers using the replyTo feature.
More control over threading options for connectors and components. Threading for Message Receivers and Dispatchers can now be controlled separately per connector.
Thread Pooling now uses the oswego concurrent library.
The sample mule webapp is a simple demonstration of how to embed mule into a webapp. It also provides an example for using the Servlet provider.
You can now transform messages using Mule’s new Groovy transformers, thanks to Ian de Beer.
You can now split up your mule configurations into smaller units i.e. one config file per component.
It is now possible to use wildcard endpoints for receiving events, for example, the following would match 'mule.event.queue' -