You can now modify your configuration files and custom classes and have them reloaded without having to restart Mule.
Here is a quick summary for deploying an app 'foo':
Create a directory under
Jar custom classes (if any), and put them under
Place the master Mule config file at
$MULE_HOME/apps/foo/mule-config.xml(note that it has to be named
Start your app with
mule -app foo
As a bonus, application’s master config file is monitored, so if there are any class changes you want to pick up or simply modify the config, save or touch
mule-config.xml and Mule will hot-reload the application.
Mule checks every three seconds for updated configuration files under the
$MULE_HOME/apps directory, and when it finds one, it reloads the configuration file and the JARs in that applications lib directory.
Therefore, if you want to change one of your custom classes, you modify and rejar it, copy the updated JAR to the lib directory, and then touch or save the configuration file. Currently, Mule checks only the first configuration file in your application’s directory, so right now hot deployment works best with applications that have a single configuration file.
Starting with Mule IDE 2.1.1 hot deployment is automatically enabled when you create a project that is associated to a Mule 3 distribution. Read all about the hot deployment builder in the [Mule IDE user guide].