Have you considered using Spring managed beans an inject them into your various components?
D.
On Thu, Aug 7, 2008 at 1:54 PM, richrem
<rich@...> wrote:
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
--
View this message in context: http://www.nabble.com/is-muleContext.getRegistry%28%29-the-right-place-for-application-wide-runtime-info--tp18879443p18879443.html
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
