Over a million developers have joined DZone.

How to Resolve Schema Conflicts in Mule Flow

DZone's Guide to

How to Resolve Schema Conflicts in Mule Flow

Learn how to resolve schema conflicts occurring when you import a project built in an older version of the ESB into Mule Flow.

· Integration Zone ·
Free Resource

The State of API Integration 2018: Get Cloud Elements’ report for the most comprehensive breakdown of the API integration industry’s past, present, and future.

When you import a project built in an older version of ESB runtime into a newer version, you will face schema conflicts of some connectors when you try to compile that project. You can resolve those conflicts by updating the schema version of that specific connector to the new, or “current,” version.

When you open an XML file in MuleSoft there you can find the XML Configuration tab. In the XML Configuration tab, you can see the XML generated against the shapes in the message flow. In XML, you can find the Mule tag, which is the root tag of XML documents. You can find the schema references of all connectors and processors in the “Schema Location” attribute of the Mule tag.

Image title

In the above XML, you can see that the highlighted schema references a specific version; you have to replace that specific version with “current.”

Now the updated Mule tag will look like this:

Image title

Your API is not enough. Learn why (and how) leading SaaS providers are turning their products into platforms with API integration in the ebook, Build Platforms, Not Products from Cloud Elements.

mule 3.7 ,schema ,conflict

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}