Hi,
As it has been discussed on the user list and in JIRA issue
*TAPESTRY-733 <http://issues.apache.org/jira/browse/TAPESTRY-733>*, the
order of pageBeginRender invocations often needs to be in the order of
the page first, to the inner most components last. At the moment the
order is undefined.
Since the listeners are currently invoked in the order in which they are
added, they are added in the finishLoad() methods, they are therefore
invoked in precisely the opposite order -- inner-most components first
and page last.
One simple modification would be to change AbstractPage, so that the
listeners are invoked in the opposite order in which they are added.
This small change would take care of *TAPESTRY-733
<http://issues.apache.org/jira/browse/TAPESTRY-733>* and a number of
other issues. Does anyone see a problem with this approach?
The long time solution would of course be to abstract the whole listener
logic into a HiveMind service, and perhaps declare the order of
invocation in its configuration. But the above modification can happen
immediately with multiple positive effects.
- mb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
