Posted by Lipika Naik on 16 November 2018
DataWeave is the primary transformation language in Mule. What is interesting about DataWeave is that it brings together features of XSLT (mapping), SQL (joinBy, splitBy, orderBy, groupBy, distinctBy operators), Streaming, Functional Programming (use of functions in DataWeave code) to make it a power-packed data transformer. I am going to discuss some of the scenarios which will help developers solve some difficult problems using DataWeave. The three topics I would like to discuss here are:
Posted by Edward McLoughlin on 29 September 2015
The groovy script transformer component is a very powerful piece of Mule. I use it for almost every message transformation that I need to make. Its XML and JSON libraries reduce message format conversion down to little more than building a map, while closures give you some powerful processing tools for handling complex data structures.
Posted by on 16 September 2014
While working for one particular client we were under the particular constraint of not having access to the JMS management console (in this instance the ActiveMQ Console). So when it came time to test out integration workflows we needed a quick and easy way to call the SOAP over JMS services. The Deloitte Platform Engineering folks are well versed in their Groovy scripting and came up with this awesome Groovy script:
Posted by on 02 December 2013
Part 1 of this series layed the foundation for some Groovy concepts and what makes the language suitable for data mapping tasks. With that in mind, lets dive into some of the advanced mapping features and some real world samples.
Posted by on 14 November 2013
ESB services involve working with a variety of different data formats and structures e.g. XML, JSON, CSV, spread sheets, key-value structures. Transformations between XML and other data structures are quite common when it comes to developing an ESB layer. Mule ESB provides a wide range of choices when it comes to scripting and data transformation. There’s enough choice to satisfy the proclivities of any developer.