If you ever used Mule 3, then there are probably two things about error handling you already know:
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.
All hail DataWeave!
One of the major changes in Mule 4 is the introduction of DataWeave as our primary expression language. Although this may seem like a radical change, I’ll explain some of the reasons behind our decision, and why this represents a major leap forward. I’ll also share some examples and answer a question that is likely on many readers’ minds: “what about MEL?”
As you might have read, Mule 3.8 includes a number of improvements regarding TLS. In this post, we will analyze the TLS environment prior to this release and explore all of the new enhancements in detail so that you can start taking advantage of them.
Last year, while we were discussing sponsoring an organization supporting women in technology, an idea came up: doing something ourselves. We thought about what we wished we had known before starting our careers and all agreed we would have liked to know upfront what the job looked like: what work we could actually do, which roles we could have and how was the day to day in a tech company. An open house seemed like a great way to show what life in MuleSoft is like, so we invited students in technology related careers to visit our offices in Buenos Aires and get a glimpse at the tech world.
A while ago MuleSoft started considering sponsoring an organization supporting women in technology. There were many to choose from but we wanted to work closely with an organization that would allow us to be very involved. We also wanted to be inclusive since technology is not just about coding. Luckily, we learned that a new branch of Girls in Tech was getting started in Argentina and were looking for sponsors to organize a hackathon, so we jumped in.
For a while now there have been maven archetypes for creating mule apps and domains. Such archetypes make getting started with development easier by automatically generating the basic core structure and files of mule projects (think configuration files, test classes, pom). This is especially interesting since the introduction in 3.5.0 of shared resources through mule domains which could make your app depend on another external project (a domain) and using Maven to manage dependencies makes perfect sense. We will see how to use these archetypes to create a domain and an application that uses it.
Testing is essential to all code, it’s a warranty on the expected behavior and a measure of quality. Having a large and thorough test suite increases the confidence we have on a system. That’s why Mule offers a number of options for testing, like our Functional Test Framework or MUnit, a good example of the former being FunctionalTestCase.
By extending from this class we can create our own tests around a Mule configuration XML file (or ma
ny) that will be run as an app in a Mule server. We can then run flows or use MuleClient to send requests and verify that the responses are the expected ones, for example.
Sign up for our newsletter
