Configuring integration projects using Mule ESB involves XML, and 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. The recently released Mule 3 tackles this problem with the introduction of pattern-based configuration.
 
With pattern-based configuration, the Mule project team has started an effort to collect and implement commonly used configuration patterns within Mule 3, enabling developers to perform common configuration tasks with the least possible amount XML. Pattern-based configuration will allow Mule ESB to continue widening its lead among other open source ESBs, such as ServiceMix and OpenESB, in terms of configuration simplicity.

Read more about pattern-based configuration in Mule

The Mule team has published a series of articles with details on the first handful of configuration patterns that are included with the most recent Mule 3 release:

• Simple service - a simple way to expose request-response services
• Web Service proxy - short and easy configuration of a web service proxy
• Bridge - a common and essential building block for integrating systems
• Validator - provides up-front data validation of incoming messages

What are some other common configuration patterns you’d like to see implemented?

Download the open source Mule 3 here.

Mule 3's features sound great. Does someone has any decent example how to comply with the license's attribution clause on a web-based application? What if the web layer is not really aware that there is a mule esb behind it (because it is accessed through various abstractions and other layers)?