Sharing Custom Configuration Patterns

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.

Mule supports the notion of configuration patterns that are specialized flow tailored to serve a very specific purpose in the least amount of XML.

For a list of configuration patterns that ship with Mule, see Using Mule Configuration Patterns.

Mule also provides the necessary tooling for creating a pattern catalog and patterns within it, allowing teams to encapsulate domain specific knowledge in custom configuration elements and share it across teams.

In essence, a pattern catalog is not different than a standard module: teams sharing pattern catalogs will only need to add a new dependency in their pom.xml. Of course, unlike what it’s done with Mule standard modules, the dependency scope will have to be "compile" and not "provided."

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub