One of the strengths of the Mule ESB is its ability to share many kinds of resources with the rest of the software environment: libraries, Spring beans, transaction managers, and many more.  Starting in Mule 2.2.6 and 3.0, there’s another thing Mule can share: transactions.
(more…)

Configuring Mule involves XML, and though using a decent XML editor can help a lot (thanks to the contextual help it provides from Mule’s schemas), there is still a enough angle brackets to warrant a coffee break as projects get more complicated.

As the number of services in a Mule project increases, so does the amount of noise in its configuration files, making it harder to understand and maintain them. We recommend splitting service configuration files, but in Mule 3 we’ve decided to go further and tackle this problem with the introduction of pattern-based configuration.

(more…)

When you take a look at the examples that come with the latest Mule 3 milestone release, you’ll notice that endpoints have an exchange-pattern attribute now:

This attribute replaces the synchronous attribute we used before. Why did we change the configuration? The old synchronous attribute was purely a two-way state: it was either true or false. With the exchange-pattern attribute on endpoints we’re free to allow additional values in the future. Also, the term exchange pattern is more accurate than the old synchronous flag. When you define the exchange pattern “request-response” on an inbound endpoint, it’s clear that you are expecting a response.

(more…)

Though a veteran language and platform, Erlang has recently gained a lot of traction, as very visible web sites and open source projects decided to use it in order to leverage its intrinsic support for highly concurrent, fault tolerant and distributed applications. To name a few, let’s mention: Facebook Chat, Mochiweb, ejabberd, RabbitMQ, riak and CouchDB.

Without opting for Erlang as a development platform, companies may still be tempted to leverage an Erlang-built middleware: most of them offer public interfaces accessible over generic protocols, like HTTP, and are easy to integrate quickly and efficiently. That said advanced scenarios can require a tighter integration like, for example, creating a module for ejabberd that requires to call custom Java code or reaching server functions on RabbitMQ that are not accessible through AMQP.

This is when the Duke meets Erl. And this is when Mule ESB can help, thanks to the new and coming Erlang Transport for Mule 3. Read on for more information about the transport and a walk-through a simple use-case of RabbitMQ integration. (more…)

The Mule ESB team is happy to report that we published the next milestone on our journey to a final Mule 3 release. The focus of Milestone 3 was mostly on internal architecture changes. Some highlights:

• MuleMessageAdapter has been dropped, replaced with MuleMessageFactory (read more in this post)
• Lifecycle improvements and fixes, although that may affect only users coding against Mule APIs, like custom transport creators (read more here)
• Support for Axis transport is being phased out gradually. Enterprise customers would still be able to obtain the transport from the portal to ease migration to Mule 3
• An early preview of the new deployment model for Mule applications, drool over the details here.

Download it
Release notes
Provide feedback

Enjoy!

Mule 3 Milestone 3 (3.0.0-M3) is ready to hit the streets, and today we’d like to talk about a fundamental transformation that it has undergone. Mind you, it’s not the only one

(more…)