Re: is muleContext.getRegistry() the right place for application wide runtime info?

Thanks for the response, but I don't think this would work for the underlying purpose, which requires learning of changes that occur during runtime.  I need to store cached information that is updated periodically when changes occur and make it available to the security system.  The other components need to reference this cached information at runtime as well.

It's possible I'm missing something very obvious, though...

Please see my other post, which you can find at [http://www.nabble.com/How-to-handle-dynamic-ACL-type-updates--tt18879529.html] and let me know if this changes your thinking any.

Cheers,
Rich

ddossot wrote:

Have you considered using Spring managed beans an inject them into your
various components?

D.