Yes, that's possible when using preserveDataMode=true; but then how can i avoid loading the entire table data from the database after each action? preserveDataModel won't pass the entire table data between requests, so every time i make some changes (delete some rows), the backing bean which holds the table data is reinstantiated and then getTableData is invoked...so if i don't initialize (get it out from the database) the table data in the contructor or in the getTableData method then nothing gets displayed after the user hits the delete button...
I think, an example of a data table in which are showned these basic actions that need to be made on a data table, add or remove some rows, and the entire table data is passed between requests not kept in the user session, would be very usefull. In don't know if this is possible right now.
Manfred Geiler <[EMAIL PROTECTED]> wrote:
Manfred Geiler <[EMAIL PROTECTED]> wrote:
Catalin,
Do not use x:saveState for the dataTable list.
Use preserveDataModel attribute in x:dataTable instead and let your
model bean get updated by implementing a setter method ("setList") for
the value property that is responsible for providing the list for the
dataTable. This way you will get back the updated dataList with the
right checkbox boolean properties.
Manfred
Catalin Kormos schrieb:
> Hi Manfred, thanks for you interest,
>
> The dataTable is nested inside of a form, and the delete button(link)
> doesn't have the "immediate" attribute set to "true" unless this is the
> default value, because i have't specified it at all.
>
> I've resolved the problem by keeping the list of data the table displays
> in the user session, because i've realized that x:saveState won't get
> the right state, it does't get the data with the selections made; it
> seems that x:saveState gets the table data before any changes are made
> on the items of that list (the selection value is not submited yet). Is
> this possible?
>
> Thanks
>
> */Manfred Geiler <[EMAIL PROTECTED]>/* wrote:
>
> Catalin,
> Please make sure:
> - that your dataTable is nested within a form
> - that your delete button does *not* have the immediate attribute set
> (necessary to get the checkboxes updated)
>
> Manfred
>
>
> Catalin Kormos schrieb:
> > Hi,
> >
> > I have a x:dataTable that displays rows over multiple
> > pages...the scenario is pretty simple, i think, a
> > table with many rows, the user can select one or more
> > rows by selecting a coresponding checkbox on the firs
> > column, and hit a "delete" button, or link to remove
> > those rows from the table. The value, selection, of
> > the check box is bound to a boolean property of the
> > row's bean, that has getter and setter.
> >
> > The first time the user selects some checkboxes (rows)
> > and hits "delete", everything works fine, the rows are
> > removed, page reloaded...; then, the user does nothing
> > else, just selects some rows again, then hits
> > "delete"... nothing happens!, because the backing bean
> > is not informed about the new selections.
> >
> > The problem disapears if after the first delete
> > action, the user uses the dataScroller to navigate to
> > a another page, or does a page reload by hand...
> >
> > Maybe has do to with the following things : i use
> > client side state saving, the x:dataScroller,
> > preserveModel is false for me, i use the x:saveState
> > to save the table data list displayed between
> > requests....
> >
> > Any ideeas would be appreciated, i realy think this is
> > a bug in myfaces, i saw some other threads about
> > dataTable updating children components, could be the
> > same problem?
> >
> > Thanks
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - Find what you need with new enhanced search.
> > http://info.mail.yahoo.com/mail_250
> >
> >
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
