I still wondering, though, why Global is not a good place, after all Globals are context attributes also and Tapestry manages them pretty well.
-Harish
Christian Essl wrote:
What if you had two applications running under the
same context though?
I guess they should have (as recommended by the servlet-spec) have attribute names like [package-name].HiveMindRegistry. (Of course if you mean two Tapestry apps you will have to find another way).
And how will replication be taken care of, I thought
context attributes are not replicated in a clustered environment.
As I see the war is distributed and on each node it will be started up seperately. Therefore the ServletContextListener. However I am not so common with clusters.
And,yes the constructDefaultRegistry will definitely be helpful.
-Harish
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
