Hello all,
I just wanted to hear if current state of page configuration and activation
is the desired one? (this is the reason for one of my architectural
problems, but I don't want to go into details here since it will boil down
to - why don't I use RequestFilters insted of page hiererchy for some common
preprocessing actions)
Documentation states that page configuration via @PageActivationContext and
@ActivationRequestParameter fields is done prior to calling "activate"
handler, but it doesn't state what happens when one has page hierarchy.
Prior to version 5.2.1 (I think), page configuration via
@PageActivationContext and @ActivationRequestParameter was totaly separated
from "activate" handler. For example, @PageActivationContext field in
subclass was always set prior to calling "activate" in superclass.
With version 5.2.1 it changed in such way that these annotation are kinda
tied with "activate" and handled in bundle with it. For example, when
"activate" is being handled, Tapestry first takes superclass, sets
@PageActivationContext field and calls "activate" on it, then it takes
subclass, and again sets @PageActivationContext field and calls "activate"
on it. In other words, "activate" handler in superclass is called prior to
@PageActivationContext field in subclass.
Is this behaviour as it is supose to be?
Regards,
Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
