Mule does have those, the session, but it's not really a good fit for your use case.
Andrew
On Sat, Aug 9, 2008 at 1:11 AM, richrem
<rich@...> wrote:
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
>
>
View this message in context: http://www.nabble.com/is-muleContext.getRegistry%28%29-the-right-place-for-application-wide-runtime-info--tp18879443p18902303.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
