Re: [mule-scm] [mule] branches/mule-3.2.x/core/src: MULE-6405 - invalidating cache after undeploying a mule app
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.