Hi!
The idea is (if running in an environment which allows this (JSF >=
1.2, facelets) to:
a) scan the JSF tree after it has been created and before it is going
to be rendered
b) collect the required resources during creation of the tree
Both possibilities are in wrong place - if all resources were to be
caught, it has to scan tree after all modifications - after
INVOKE_APPLICATION phase.
Yep, then it might work in an phase listener for the postback, but not
for the initial rendering. Maybe we have to differentiate. But as I
said, I think those resource should be rather static and simply are
configured by the component then.
The Renderer has to implement that interface then.
Implementing interface would break TCK test of JSF spec.
I meant the concrete Renderer e.g. HtmlCalendarRenderer.
Wouldn't simple splitting output of whole page to 3 (or 4) independend
chunks do the trick (HTML example):
1st for whole head w/o finnishing </head> tag
2nd starting with </head> <body> to the inserting spot for styles (not
sure of this splitting)
3rd for whole body w/o ending tag </body>
4th ending body + html tags
You still have to buffer the output, no?
I don't like buffering. It slows things down and the very most important
thing for a webapp is to start rendereing so the page transitions on the
client happen soon.
Ciao,
Mario
