Mule 4: Java Integration static methods with dreamweave
Experienced Mule users will notice that Mule 4 takes a more opinionated approach about how to structure apps, which limits what can be done through the expression language. The intention is to provide a clear separation between the flow logic and the business logic that should be extracted through code. If you want to extract, query, transform, or otherwise work with data in your flows, DataWeave expressions and transforms are the recommended tool. If you want to write custom logic, instantiate Java objects, or call arbitrary methods, MuleSoft Developer Training recommends that you encapsulate this code into scripts or classes that can be injected and tested easily. This is why MuleSoft removed the Expression component and Expression transformer in favor of encouraging you to cleanly separate your logic into scripts or Java classes, instead. Calling Static Java Methods from DataWeave When you want to call out to Java logic to help format or parse data, DataWeave now allows you t...
