Last month we released Mule 3.3 M1, our first milestone on the way to Mule 3.3. While for production you should use Mule 3.2.1, we hope these milestones are a great way to play around with the latest and greatest features. This is a great opportunity to provide feedback and have an impact on what we are doing for the Mule 3.3 release.
Continuing my previous blog post Error Handling Patterns in Mule, in this post I will show you how to implement the following use cases:
- Rollback transaction and send notification email
- Stop flow execution based on exception type
With a Mule and a Toad involved, one could expect that a third character would quickly need to be added to the cast: a princess to ride the former and kiss the latter. But then, what would be so exceptional about it? Because, actually, this story is about exceptions and their graceful handling. Moreover, the story takes place in the clouds, and princesses don’t fly so well…
So let’s come back to our main protagonists: you know Mule ESB already but you may not have heard about Hoptoad,