yah, this is little confusing, since it will place the CustomLinker
first in the list of filters.. :) But they "execute" as they come out
of the list.. :)
CustomLinker -> DocumentLinker -> RenderSupport -> PAGERENDER
So as the page render unfurls, it gives control to RenderSupport to
modify the DOM, then DocumentLinker, then CustomLinker. And the
document linkers really don't do anything by themselves, and require a
RenderSupport to feed them the script/css links. So the RenderSupport
filter would call environment.peekRequired(DocumentLinker.class), which
would return the deepest DocumentLinker at the moment (the default, not
the Custom one)..
So yeah a little confusing.. :) :)
Thiago H. de Paula Figueiredo wrote:
Em Thu, 29 Jan 2009 15:14:40 -0300, Fernando Padilla <f...@alum.mit.edu>
escreveu:
No. DocumentLinker would be run first ( deeper in the markup filter
chain ), it would be the only one that RenderSupport would bind to (
RenderSupport does a environment.peekRequired ). So only that
DocumentLinker would do it's stuff.
Even when the custom document linker is explicitly added to the
OrderedConfiguration *before* the normal DocumentLinker? If yes, well,
the contribution overriding mechanism in T5.1 will be extra handy . . . :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
