Mariano Gonzalez

Welcome to the final post in the three post series about batch improvements on Mule 3.8! The last new feature we have is a

Welcome back! Following the series about new batch features in Mule 3.8, the second most common request was being able to configure the batch block

Hello there! If you've been using Mule for a while now, you probably remember that the batch module was introduced back in the 3.5

This all began with a very popular request: "We want to be able to throw an Exception from a flow". The motivation for this is

A high-reliability application (one that has zero tolerance for message loss) not only requires the underlying ESB to be reliable, but that reliability needs

Currently, Mule relies on plain old java serialization in order to store objects to files or to replicate them through a Mule cluster. That

A popular request among users of the Batch module is the ability to grab the job instance id in any of a Batch job's

This is a follow up to the last post in which we discussed performance improvements on our XPath functionality obtained from the revamped XPath

Sometimes (more often than we think), less concurrency is actually more. Not too long ago, I found myself in a conversation in which we were

Howdy! This is the last post of the Mule 3.7 series Be sure to check out the other posts in the series: A sneak