[mule-dev] Re: [mule-scm] [mule][24841] branches/mule-3.2.x/core/src: MULE-6405 - invalidating cache after undeploying a mule app

[Daniel Feist]

This is kind of ugly:

i) The ExceptionHelper is not the one disposing the app, yet method name might make you think it is.

ii) Static call here isn't ideal, isn't there another mechanism?  Preferably we shouldn't store application state in static (multi-application) scope.  An alternative to this static call in MuleContext is to listen to MuleContextNotification and do cleanup then.

Dan

On Aug 27, 2012, at 1:34 PM, pablo....@codehaus.org wrote:

Modified: branches/mule-3.2.x/core/src/main/java/org/mule/DefaultMuleContext.java (24840 => 24841)

--- branches/mule-3.2.x/core/src/main/java/org/mule/DefaultMuleContext.java	2012-08-27 16:20:58 UTC (rev 24840)
+++ branches/mule-3.2.x/core/src/main/java/org/mule/DefaultMuleContext.java	2012-08-27 16:34:36 UTC (rev 24841)
@@ -40,6 +40,7 @@
 import org.mule.api.transaction.TransactionManagerFactory;
 import org.mule.client.DefaultLocalMuleClient;
 import org.mule.config.DefaultMuleConfiguration;
+import org.mule.config.ExceptionHelper;
 import org.mule.config.i18n.CoreMessages;
 import org.mule.context.notification.MuleContextNotification;
 import org.mule.context.notification.NotificationException;
@@ -280,6 +281,7 @@
 
         notificationManager.dispose();
         workManager.dispose();
+        ExceptionHelper.disposeApp(this);
 
         if ((getStartDate() > 0) && logger.isInfoEnabled())
         {