Mule Speaks Java: Towards a programmatic configuration of Mule
True to our goal of simplifying the configuration of Mule, we will be adding the capacity to programmatically configure Mule 3 in the coming
Pattern-Based Configuration: Hello Validator!
The pattern-based configuration series continues! After a first set of fairly generic patterns, this new addition will demonstrate how highly specialized patterns can provide
Pattern-Based Configuration: Hello Bridge!
Web Service Proxy was the last configuration pattern presented in this blog. Time for a new one! Connecting systems together is one of the
Configuring Message Processors on Endpoints
One of the big architectural changes in Mule 3 is that everything has become a Message Processor1. What is a message processor? It's a
Pattern-Based Configuration: Hello Web Service Proxy!
After the introduction of Simple Service, the configuration patterns series continues! The second pattern we would like to introduce is Web Service Proxy. Proxying
Pattern-Based Configuration: Hello Simple Service!
As announced before, Mule 3 will offer pattern-based configuration artifacts that will allow you to perform common configuration tasks with the least amount of
Hot Deploy from Mule IDE
The Mule IDE does not natively support Mule 3's new application structure yet, but not to worry, with the new 2.1 release of the
Improvements to exception handling for Mule 3
Background You may recall that in Mule 2.x, there were two places where you could configure exception handling strategies: 1. on the service 2.
Springing into Tcat
Spring has become a highly popular framework for the development of web applications, thanks to a compelling support for web features, both at its