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. and the default DocumentLinker
throws an exception if the root node is not html.. (adding an option to
change the fail-fast, into a quiet-fail would be good)
But please be aware, like I said before, you are overriding the default
documentLinker, so that means that your document linker would have to
support both html root nodes, and whatever root node you want....
Thiago H. de Paula Figueiredo wrote:
Em Thu, 29 Jan 2009 14:42:47 -0300, Dude.Checkitout
<[email protected]> escreveu:
I created my own CustomDocumentLinker extending from the tapestry
DocumentLinker and modified the code to fit our needs. But I have no idea
how to make Tapestry to use CustomerDocumentLinker instead of its own
DocumentLinker.
Contribute you own DocumentLinker to the MarkupRenderer service.
Something like this in your AppModule class or any other Tapestry-IoC
module class:
public void
contributePartialMarkupRenderer(OrderedConfiguration<PartialMarkupRendererFilter>
configuration) {
configuration.add("CustomDocumentLinker", new CustomDocumentLinke(),
"before:DocumentLinker");
}
I haven't tested it, but that's what I would try. :)
By the way, a good knowledge of Tapestry-IoC is not required to use
Tapestry, but it helps a lot. ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
