In previous article I have described how to create a custom domain project. This time we will try to consume that. In other words we will attach Mule application to our previously defined domain.
Recently I have finished reading Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf. This book presents in a structured way a lot of design patterns for message oriented integration solutions. It is also recommended reading made by MuleSoft on their Solution Design training.
In the previous article I have described how to share common functionality encapsulated in flows and subflows. This time I will focus on common configuration that should be shared among our applications. Mule has offered domain application that can solve
I found it crucial to be able to share some logic, encapsulated within (private) flow or subflow. In Mule ESB we have a couple of ways to handle that scenario. I will focus on custom maven project. You will see
It is always desirable to reuse as much code as possible. We can do the same regarding to DataWeave transformations and custom functions. In this article I will describe how to reuse code in newest DataWeave using modules. For those of you, working with DataWeave 1.0, I will describe how to reuse code with readUrl function.
During transformation to JSON often I do not want null properties. It is easy to remove them, by just using skipNullOn attribute. However for empty objects it is not that trivial, especially when you have to deal with many such cases within one transformation. In this article I will show you how you can achieve this quick and easy.
Content Enricher is definitely an useful integration pattern. It allows easily enrich message content with new data gathered from external resource. In vast majority of Mule’s apps I have been using Message Enricher Component. Today I will point main differences
In this brief article I will describe the problem and solution that I have lately faced. As it is a good practice not to hard-code connection data I have extracted them to external file called connection.properties. I did not expect to receive an error something like $[smtp.host]. I did not know what it can means. Below I have described what it is.
After I have passed mule Integration Professional exam I got a lot of questions from the community. What materials did I use? What are the main points to learn. What to expect on the exam. I have decided to share some of my experience with the certification. In this blog’s post you can find all materials that I have used.
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