Miller, John wrote:
Ahhh Thank You, if I had only looked at the buffer example earlier I could have
saved many hours.
This worked, however I don't like how a page developer needs to worry about when the rendering is
called . You should be able to just lay components out on a page and not have to worry about when
the model is updated. As a suggested enhancement to dataScroller (and any other component that has
a "for" attribute) the encode method should be able to do the buffering automatically
(maybe callback to the component its for attribute references) that way you can lay these
components out before the component they are "for"
Could someone who is also on the dev group please forward this thread there as
a suggestion. Thanks for the help.
I expect this problem is due to the fact that JSP pages are rendered in
one pass. Components therefore must be rendered in order.
Using something like Facelets instead of JSP fixes this; Facelets makes
two passes so all components are correctly set up before rendering. The
next version of JSF depends on a new version of JSP that (somehow) also
allows this multiple-pass thing to happen.
As the JSF1.2 expert group had to resort to modifying JSP in order to
fix this problem, I doubt that MyFaces is going to be able to resolve
this issue in its 1.1 implementation.
Regards,
Simon
