I have lots of experience playing with that :) (since we publish to
html, fbml). Here are some questions:
1) do your documents have a root node? what is it?
2) do you want to change the behavior of how it includes javascript and
css? Or just have it work with non-html root nodes?
Dude.Checkitout wrote:
We have a requirement of tml file being delivered without <html> as the root
context. As I read the tapestry source, this validation is done in the
DocumentLinker.
In contributeMarkupRenderer method:
MarkupRendererFilter documentLinker = new MarkupRendererFilter()
{
public void renderMarkup(MarkupWriter writer, MarkupRenderer
renderer)
{
DocumentLinkerImpl linker = new
DocumentLinkerImpl(productionMode, scriptsAtTop);
environment.push(DocumentLinker.class, linker);
renderer.renderMarkup(writer);
environment.pop(DocumentLinker.class);
linker.updateDocument(writer.getDocument());
}
};
Is there anyway I can override my own DocumentLinker with Tapestry's
DocumentLinker?
In the Post, "http://n2.nabble.com/-T5--A-root-element-of-<html
-is-needed-when-linking-JavaScript-and-stylesheet-resources.-td1470668.html#a1470762">http://n2.nabble.com/-T5--A-root-element-of-<html>-is-needed-when-linking-JavaScript-and-stylesheet-resources.-td1470668.html#a1470762
Howard said we can override the internal DocumentLinker.
Can anybody suggest me on how to do?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
