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. -----Original Message----- From: Mathias Brökelmann [mailto:[EMAIL PROTECTED] Sent: Thursday, December 22, 2005 5:06 AM To: MyFaces Discussion Subject: Re: dataScroller implementation take a look into the t:buffer component 2005/12/21, Miller, John <[EMAIL PROTECTED]>: > > > > > This is related to the "RE: Tobago SheetRenderer calls getter for list > twicely." Thread. > > > > It appears that where the dataScroller is on a page determines when in the > lifecycle it obtains information about the dataModel. > > I have a datable with a dataScroller on the top and bottom. There is a > button that toggles whether the Table shows "Closed Events" or not . It > appears that the dataScroller on top renders itself before the dataTable is > updated, hence showing an incorrect number of pages. See the below code : > > > > <t:commandButton value="Hide Closed Events" > rendered="#{eventDataList.showClosed}" > > actionListener="#{eventDataList.togleShowClosed}" /> > > <t:commandButton value="Show Closed Events" rendered="#{! > eventDataList.showClosed}" > > actionListener="#{eventDataList.togleShowClosed}" /> > > > > > > <h:panelGrid> > > <t:dataScroller for="events"> > > ... > > </t:dataScroller> > > <t:dataTable id="events" value="#{eventDataList.data}" > > > ... > > </t:dataTable> > > > > <t:dataScroller for="events"> > > ... > > </t:dataScroller> > > <h:panelGrid> > > > > > > The getData method must go to the DB every time, hence is not a true getter, > but unfortunately obtaining data from the DB every page request is a > requirement. > > > > > > > > NOTICE: This message, including all attachments transmitted with it, is for > the use of the addressee only. It may contain proprietary, confidential > and/or legally privileged information belonging to Litle & Co. No > confidentiality or privilege is waived or lost by any mistransmission. If > you are not the intended recipient, you must not, directly or indirectly, > use, disclose, distribute, print or copy any part of this message. If you > believe you have received this message in error, please delete it and all > copies of it from your system and notify the sender immediately by reply > e-mail. Thank you. -- Mathias NOTICE: This message, including all attachments transmitted with it, is for the use of the addressee only. It may contain proprietary, confidential and/or legally privileged information belonging to Litle & Co. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, you must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message. If you believe you have received this message in error, please delete it and all copies of it from your system and notify the sender immediately by reply e-mail. Thank you.
