Hmmm... Do you want to look at AutoUpdateDataTable?
We have implemented a way of fetching data from the server, and if the state of the server changes, to change the state on the client as well (replacing the input hidden field on the client with the new state returned from the client). If I understood you correctly, this would be what you need as well! regards, Martin On 8/30/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Hi this question goes very deep into the structures of jsf. > > I did some 1:n relational programming today, the idea was to have > a master form with the :n relational data in a subarea of this form. > My idea was to bypass the entire refresh cycle by using ajax for the > display of the :n relational data, that did work execptionally well > although it is plain html at the current stage. > > I also did the create and update cycle of the data with popup boxes > which trigger the ajax releoad at the end of their operations, worked > also exceptionally well. > > Bit I ran into one minor problem I am not sure how to solve. > Currently I keep the :n relational data due to easier handling in the > session, and use saveState only for the dialog handling of the popups. > I would love to push the :n relational data into saveState as well, but > the main problem is, with my ajax request I am kindof out of the entire > JSF lifecycle, but saveStating the data would guarantee that at the next > page refresh of the main master form the data would be loaded properly > without having to put the burden into the session. > > So my question, is there a way to trigger the serialization on a bean > outside of the rendering cycle, so that at cycle the altered bean gets > loaded and saved properly? > > Werner > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
