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 that it’s fairly common to run into “business errors” (errors not related to the handling and transmission of data but the data itself) which should actually be treated in the same way as a connection or system error (things like the remote endpoint is down).
Given the popularity of the request we decided to look into it and started by asking: “which are the use cases in which you would throw an exception?”.
We’re happy to announce that MUnit 1.0 (GA) is now available. MUnit is the functional test framework for Mule. This is builds on feedback from our previous release candidate and it contains many quality and usability improvements.
I’m pleased to announce the availability of our Anypoint Studio 5.3 release with the brand new Mule 3.7.2 release. This release features a new validations module, which allows you to easily validate Mule messages using a variety of built in validators. It also features many improvements such as improved ability to attach sources to runtimes and improvements to the API gateway runtime experience in Anypoint Studio.
Have you ever wanted to learn best practices from MuleSoft’s technical experts? Are you an architect, developer, or manager looking to implement your first MuleSoft use case? Want to experience a one-of-a-kind integration workshop AND have tasty cocktails?
I am excited to announce the latest update to the Anypoint Platform. This update is focused on a number of capabilities that enable even more efficient management of a well-oiled API-led connectivity solution.
Rich API product offering through layered service level agreements
Anypoint Platform Service Level Agreements (SLAs) allows API owners to define the menu of offerings available to API consumers.
This post is the last in a three-part series covering the IoT projects that came out of our first internal hackathon of the year, and that we had on display at our first Integration of Things Zone at CONNECT 2015. Missed us there? Don’t fret, not only will you get a sense of the cool installations we built by reading the piece below, but we also share some of the code and tips that went into making them a reality.
If you have read the Mule ESB 3.7 release notes then you already know what I’m about to say, but just to recap, here we go…
A lot of effort was put in 3.7 to upgrade our libraries stack. That effort actually began in 3.6, and although the list of upgraded libraries is not so big as it was on that release, it’s somehow more significant given that we upgraded some dependencies that we held very close to our hearts and core.
The idea of this post is to clarify some concepts around metadata, what is it, where is stored, how to use it and how it help us to develop our applications.
So, what is it? Metadata is a term used in many places in the Software industry and its meaning may vary depending on what it’s used for. In the context of Anypoint Studio we are always talking about types and types related information.
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 to extend to individual connections. If your application uses a transactional transport such as JMS, VM, or DB, reliable messaging is ensured by the built-in support for transactions in the transport. This means, for example, that you can configure a transaction on a JMS inbound endpoint that makes sure messages are only removed from the JMS server when the transaction is committed.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.