Using Mule with Spring
|MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.|
Mule leverages the Spring framework for developing Java applications.
Mule 3.8: Spring 4.1.9 and Spring Security 4.0.4
Mule 3.7.5: Spring 4.1.9 and Spring Security 4.0.4
Mule 3.7.0 - 3.7.4: Spring 4.1.6 and Spring Security 4.0.1
Mule 3.6 and earlier: Spring 3.2 and Spring Security 3.0
See also: Spring Security Migrate 3 to 4
The way to configure a Mule application is with an XML file that uses custom Mule namespaces. By default, a Spring configuration builder takes this XML file to create Mule artifacts and register them with a Mule runtime instance.
Use one of the two namespaces in your Mule XML Configuration file:
Mule’s XML configuration file takes advantage of Spring 4.1.6’s ability to create bean definition profiles. You can use Spring bean definition profiles to register different beans for different target environments, instead of using one bean for all target environments. For more information, see Bean Definition profiles in the Spring Framework Reference.