Access Keys:
Skip to content (Access Key - 0)

Mule IDE - Contents

Mission critical Mule deployment?

Try Mule Enterprise

Mule Enterprise Edition provides:

  • Hot fixes, security patches and backported bug fixes
  • High availability clustering to eliminate downtime
  • Root cause problem analysis tools
  • 24/7 support from the Mule experts

Need help with Mule?

Get Mule services

Whether you are just getting started or want to improve an existing Mule architecture, MuleSoft experts provide:

  • Onsite and online Training
  • Consulting Services
  • Enterprise Support

Mule is Hiring!

Apply now

Like working with Mule? We're looking for superstars to join our amazing team.

Eclipse XML editor

The Eclipse XML editor is part of the Web Tools Platform. Since Mule configuration files are Spring XML files by nature the XML editor is an important development tool and provides a lot of benefit. When working in Eclipse, it provides:

  • Schema documentation assistance for the element you are configuring
  • Validation of your schema and context of any errors that are detected
  • Autocomplete of elements and attributes based on what is valid in the current element of configuration you are editing

There are some known and reported Eclipse issues that impact the use of the Eclipse XML editor. We have documented and in some cases provided access to patches to work around these issues.

Schema validation (Eclipse Bug 284272)

Starting in the Galileo release, Eclipse has begun to report validation errors where none exist in Mule configuration files. This is due to the Xerces parser used by Eclipse’s WTP for parsing trying to resolve all namespaces referenced in the config file in all schemas. In order to prevent these types of validation errors when opening Mule config files, you need to disable the Honour all Schema Locations preference in Eclipse. We published a blog post that describes the symptom and directions on how to make the preference change.

Schema autocomplete (Eclipse Bug 247312)

Another usability issue with the Eclipse XML editor is that autocomplete does not always appear to work, especially when XML namespaces are used to reference elements. Configuration in Mule relies heavily on namespaces, so this makes writing Mule config files is harder than it should be. We reported the issue in Eclipse's bug tracker. The ticket has been sitting there for years but luckily someone stepped up and developed a patch. Unfortunately, that patch did not make it into an official Eclipse release yet. To aid our users and anyone else that needs this fix, we chose to bundle the patch for the popular releases of Eclipse and distribute it via our update site.

Depending on your Eclipse version, choose one of the available update sites:

Adaptavist Theme Builder (4.2.2) Powered by Atlassian Confluence 3.4.7, the Enterprise Wiki