Mule 4 Kernel – IntelliJ IDEA

Mule 4 Kernel – IntelliJ IDEA

ceived lately a lot of questions regarding Community Edition of Mule ESB in version 4. Therefore I have decided to write a couple of articles about this . First of all MuleSoft has rebranded community version into the Mule 4 Kernel. In this article I had in mind to show, how to write a simple application using IntelliJ IDEA community IDE. However this is impossible yet. You will see only how to setup Kernel runtime and what is going on with IntelliJ plugin for newest Mule Runtime. In the next article I will use Anypoint Studio instead.

Reuse driven by DataType

Raml 1.0 introduces new concept called DataType.  This fragment is used to declare type in a separate yaml file. This is not just a simplification of JSON schema to conform raml/yaml. It also brings simple improvements and syntax sugar that allows to write types in more concise form. And therefore more readable. In this article we will look at how to define own data types and reuse them in API and its implementation

Error Handling simplified – Try Scope

Errors occurs all the time. All you can do is to implement error handling. In this article I will describe how to use introduced layer of abstraction in exceptions area. Prior to Mule 4, developer only could access raw Java exception as Mule is a Java based ESB. This lead to situation where you, as a developer, needed analyse documentation to find exact exception that you would like to handle. Now an Error concept was introduced.

DataWeave – Tip #3

DataWeave – Tip #3

I have already presented how to call Java code using messages processors with the newest Java Module for Mule 4.x. For earlier mule’s version Entry Point Resolvers were used to invoke custom Java code. However for scenarios when we would like to use custom code in DataWeave, for transformations, another approach is needed. Approach presented in this article will be more concise comparing to using message processors. It was highly extended comparing to possibilities of Mule 3.x version. Mule 3 allowed to invoke static methods. In contract Mule 4 not only permits to call static methods but also instantiate classes and access its instance attributes.

DataWeave – Tip #2

DataWeave – Tip #2

Tip number 2 is about converting decimal number into integer one. This may seem tricky at first. You may say that we do not need to do anything special and DataWeave engine will handle it underneath. However there is a nuance that you should be aware of. In transformation to XML this may not actually works. This tip is primary dedicated to DataWeave 1.0 as in DataWeave 2.0 this does not occur.