well its a rather ajax specific problem...
the real problem was that we skipped the render response phase, which
calls the encode begin method (which we skip, since we only render the
content that is we only call the encodeInnerHTML method). this was a
problem, because the method nullifies the preservedDataModel... we
solved it by nullifying it ourselves...
im not yet sure whether it is allowed at all (especially since for now
we had to add some setter and getter methods in the htmlDataTable class. ;)
but so far there is no other way for us...
thanx a lot again
greetings jörg
Martin Marinschek wrote:
Great!
You want to share with us how?
regards,
Martin
On 8/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
never mind, we fixed it ;)
greetings jörg.
Martin Marinschek wrote:
No, not as far as I know.
You can easily try out the differences between preserveDataModel true
and false by having a request scoped bean on the backend which looses
its backing model upon reload and by showing links in the datatable -
without preserveDataModel = true the links will not be executed!
regards,
Martin
On 8/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
hi everybody!
i'm having troubles understanding the function of the dataTable, when
preserveDatamodel = true. Is there an example designed only for testing
this feature, someting which clearly shows the difference between the
two possibilities??
happy for any suggestions...
greetings jörg
