On May 2, 2005, at 9:37 PM, Michael Musson wrote:
Global was also a little bit of a problem for me because it doesn't know the context when it is created.
It can if you override createGlobal on a custom engine implementation - you can hand it whatever information you need to.
Erik
On 5/2/05, Paul Ferraro <[EMAIL PROTECTED]> wrote:
Not quite - the global object is instantiated along with other engine
parts in AbstractEngine.setupForRequest(...). Although, as you correctly
implicated, it is instantiated lazily, i.e. not on application startup,
but on the first request to the application.
Paul
Erik Hatcher wrote:
On May 2, 2005, at 5:15 PM, Paul Ferraro wrote:
Other locations that come to mind are: a servlet context listener, overriding the init() method of the Tapestry servlet, or the global object facility.
Global, though, will be instantiated on the first call to getGlobal()
though, not on startup. Right?
Erik
-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
