About the XML Configuration File
Use Spring XML files with custom Mule namespaces to configure Mule applications.
In a Mule application, you specify the Spring XML schema files in the header.
Be sure to specify all the necessary schema files. This can be time-consuming when setting up the configuration file, but importing schema files provides the following time-saving benefits:
- Auto-completion and context-specific help in your favorite IDE
- Design-time configuration validation
- Typed properties
Each Mule module or transport has its own XML schema. When you import a schema, it has its own namespace.
To use the standard Spring elements, import one of two standard Spring namespaces:
- http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
- http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
Typically, you set the Mule core schema as the default namespace for your configuration file. This means that any XML element without a prefix will come from the Mule core schema, (
mule.xsd). To set the default namespace schema, specify
xmlns immediately followed by the URL of the Mule schema, without the colon or namespace prefix you set in the previous example (e.g.,
xmlns instead of
Spring Bean Profile Definitions
Although your configuration files appear to be Mule-specific, they are really just Spring configuration files with Mule-specific extensions
This approach allows you to use anything Spring offers within your Mule configuration, such as beans, factory beans, bean profile definitions, resource loaders, EJBs, JNDI, AOP, and even integration with other software such as jBPM, Gigaspaces, JBoss Rules, etc.
Merging Configuration Files
If you have multiple configuration files, you can import them into one configuration file so that you only have to specify one configuration. For example: