« Return to Thread: is muleContext.getRegistry() the right place for application wide runtime info?

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

by richrem :: Rate this Message:

Reply to Author | View in Thread

Mule gurus,

I was poking around the docs for some hints/ideas/best practices for storing application wide runtime info.  I ran across the Registry object, available from a MuleContext instance.  Is this a good place to store runtime information that is needed by components or other architectural elements - e.g. routers?  Or, is there another place where I could/should store application wide info that may change over time and is fairly easily accessible to various components in the system?

Also, are there any gotchas I should be aware of with the Registry, if that is the right place to put stuff?

FYI, we're using Mule 2.0.1 currently.

TIA,
Rich

 « Return to Thread: is muleContext.getRegistry() the right place for application wide runtime info?