That's correct. Given your code, you would have:
hisDispatcher, then myDispatcher, and then PageRenderDispatcher.
Robert
On Mar 20, 2009, at 3/207:20 PM , Angelo Chen wrote:
Thanks for all the answers.
the ordering clauses, you meant something like this:
configuration.add("MyDispatcher", m
Thanks for all the answers.
the ordering clauses, you meant something like this:
configuration.add("MyDispatcher", myDispatcher, "before:PageRender");
configuration.add("HisDispatcher", hisDispatcher, "before:MyDispatcher");
in this case HisDispatcher will be executed always before MyDispatc
It's an ordered configuration; it's executed in the order specified.
In the event that the constraints don't provide a clear ordering (as
in your example), the ordering is undetermined; I wouldn't count on
any consistent ordering.
Robert
On Mar 20, 2009, at 3/209:07 AM , Angelo Chen wrote:
There is no order unless you set it with ordering clauses (such as
"before:PageRender"). The order in which the contribute methods are
invoked across modules can vary with platform, release, or just
arbitrarily. It is not specified. Likewise, the order in which the
contributed objects appear when
Hi,
what is the execution order of dispatchers, last in, first out or first in,
last out? following are my two dispatchers, which will be called first and
why? thanks.
public static void
contributeMasterDispatcher(OrderedConfiguration configuration,
