Use case-specific error handling in Mule 4

popular error types

Often times when you are processing data through a flow, you may want to treat certain errors differently than others. For instance, if you are trying to select records from Salesforce, you would want to handle a record not found error differently than an out of memory error. For this reason, MuleSoft allows us to handle errors based on use cases as well as the types of errors that are being thrown.

Mule 4 error handling deep dive

on error continue main flow

In my previous blog post, I discussed the basics of error handling with Mule 4, helped understand what a Mule error is, what the two major error handling scopes in Mule 4 are, as well as how they work. In this post, I will discuss how to take these basic concepts and build them up so that you can implement error handling strategies in your application (and not be completely lost when doing so).

Mule 4 error handling demystified

Mule 4 error handling

Like many developers and architects who build APIs and integrations, I was on top of the world when I completed the training on Anypoint Platform Development fundamentals (Mule 4); I was now able to take an idea for an API and build, design, deploy, and implement my API in a matter of hours. I now held the shiny key to become a MuleSoft Certified Developer — I just had to pass the MuleSoft Certified Developer –

A Look into Error Handling in Mule 4 Beta

error handling mule 4 beta

If you ever used Mule 3, then there are probably two things about error handling you already know:

  1. It’s really Java exception handling
  2. It’s a “trial and error” experience

In this post, I’ll explain the major changes introduced in Mule 4 around error handling, including easier routing and the introduction of our new try scope.

Announcing Mule 3.8: A unified runtime for integration and API management

As part of our upcoming Anypoint Platform June 2016 announcement, we are excited to release Mule 3.8. This release extends the flexibility of Mule, the runtime engine of Anypoint Platform, by unifying integration and API management capabilities into one lightweight distribution. It also significantly enhances core Mule functionality including DNS round robin load balancing, DataWeave Flat File, Fixed Width and COBOL Copybook support,

Error Handling in APIKit-based Projects

motif

error handlingerror handlingIf you look at the W3C document listing HTTP status codes, you may notice that only a small portion of all possible codes represents the happy path – i.e. 2xx codes. Most other codes are there to let client know that something went wrong with the request and the expected response cannot be returned. When building an APIKit-based application, developers must properly handle error conditions and set status codes accordingly. As always with Mule,

Announcing Mule 3.3 Milestone 2

February 13 2012

2 comments
motif

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.

Error Handling Patterns in Mule Part 2

motif

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

The exceptional story of a Mule and a Toad

motif

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,