hi, at the moment it is difficult to see what you already tried and which painful way of trying different possibilities you already walked along...
first of all - there is a bug at sortable and filterable tables - i already opened an issue... some details: this bug only occurs if you have a changing model within a sortable table - i guess that's not your case!? 2 further questions: - have you already tried to use component binding? - did you already give ppr a chance or did you just deactivated it? - generally ppr should work very well if nothing of both would solve your problem - i don't have further spontaneous ideas without knowing more details about your implementation... is it possible for you to provide some source code of your implementation or an equivalent example? regards, gerhard 2007/11/13, Stephen Friedrich <[EMAIL PROTECTED]>: > > Thanks for the answer. > I am not at all using PPR at the moment. Just to be sure that my problem > is not > caused in any way by PPR, I switched it off using this snippet at the top > of my page: > <script type="text/javascript" xml:space="preserve"> > // <![CDATA[ > _pprUnsupported = true; > // ]]> > </script> > > If I understand the problem correctly, the immediate flag causes all other > components > on the page to stay "unprocessed". > So the html component with the generated id "shopTimeDetails:1:threelc" > just keeps its > value, even though at row index 1 there now is a different model value. > > I just don't have any idea how to make this scenario work. > > > Gerhard Petracek wrote: > > hello, > > > > how do you trigger ppr (the update) at the moment? > > > > there are several ways to trigger ppr - to answer your question > > concerning programmatically updating components maybe the following link > > will help you: > > > http://myfaces.apache.org/trinidad/devguide/ppr.html#Using%20RequestContext > > > > regards, > > gerhard > > > > > > > > 2007/11/12, Stephen Friedrich <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>: > > > > I am desperately trying to get a specific table UI to work - see > > screenshot. > > In short I have a list-backed table model. > > When displayed there's a delete button in front of row. > > The first column is a selectOneChoice. > > There's always one more row at the bottom than there are "real" > values. > > If the user selects a value from the dropdown, then another row is > > added. > > > > Here's the catch: > > Of course, neither the delete link nor the dropdown should trigger > > validation, > > so I have set immediate="true" on them. > > > > Unfortunately now the components on the page do not update > > correctly, for example > > if I delete the second row (see screenshot) the page does indeed > > display one row > > less, but the second row still displays the same data. > > > > What the heck can I do to programmatically update the component-side > > of the model? > > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
