It is a good practice to monitor your service and check whether it is available and/or is performing as expected. In order to do this we need to specify what service’s health term means. In this article I will present two
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.
In one of my previous posts I described Java Component and entry point resolvers as a way to invoke Java Code in Mule 3.x. In this article I will focus on completely new approach in Mule 4. Mule presents brand new Java Module capable of creating new instances, invoking methods on those instances and invoking static methods. Although you can invoke Java using DataWeave 2.0 and Groovy scripting you are losing additional metadata (DataSense). So lets walk through some sample application.
What is the most important thing that a mule developer needs? I think that well configured IDE is the answer. While you can have an appropriate set of skills, without a good toolkit you wouldn’t be as efficient as you could. Therefore in this article I explain how I configure my development environment. I hope that you would enjoy it :).