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

Thanks for the response.  This would work, and suggests to me that Mule does not have anything equivalent to the web application storage maps provided for various scopes - e.g. application, session, request.  I was hoping to use something that might already be designed for this purpose.

Does anyone else think it would be a good idea to design this type of thing into Mule?  I could see sharing information across the entire application as well as in a scope larger than a simple synchronous request - e.g. choreographed and/or asynch reply services.

Rich

Andrew Perepelytsya wrote:

Wouldn't something very obvious be a simple static field reference in some
holder class?

HTH,
Andrew