On Thu, 22 Nov 2012 05:45:10 -0200, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
So now with 5.3.6, since pooling is disabled, is it a single page
instance for each request?
Yes.
And how does it differ from the activation context event if they are
both executed when the page is first loaded ?
That's a completely different thing. The singletonness of Tapestry 5.2+ is
about fields and the activation context is about invoking an event handler
method.
My *guess* is that tapestry loads the page for the first time
(@PageLoaded),
Correct.
attaches it to the client's session (that is created by
default)
That's not correct. Tapestry doesn't create an user session by default.
It's created when needed (a write to the session). In addition, page
instances aren't attached to sessions. I guess you're talking about the
per-thread map used to store the field values. If yes, then you were
correct, just used the wrong words. :)
and then executes the ActivationContext even whenever a request is made
to the page, am I correct ?
Correct.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
