I've looked into this issue once more and it seems I solved it by.. doing what Decebal said.
In the update() method of the SortableUpdateCallback, after the changes are saved to the XML data source, I call ListView.detach() directly. So the ListView gets a fresh, up-to-date version of the model. But somehow I find this solution a bit hacky. Maybe because I don't understand whats happening in detail. Shouldn't do the model all that kinda stuff for me? So I don't have to think about if I have the latest version of the model? Or is this a particular problem with the LoadableDetachableModel I just should be aware of? Also, I have to keep a reference to the ListView in a member variable now, which is something I always tried to avoid. Does that even make sense? In terms of page-size, or performance? 2012/10/31 Ernesto Reinaldo Barreiro <[email protected]> > We're sorry but all of our available download slots are busy currently, > please try again within a few minutes. > > Can you e-mail it to me directly? > > On Wed, Oct 31, 2012 at 4:17 PM, Benedikt Schlegel < > [email protected]> wrote: > > > I have no maven installed, so I can't create a quickstart. Instead, I > > zipped my project directory (an eclipse project) and uploaded it here: > > http://uploaded.net/file/d2zahfva > > > > Don't worry about the file size, all dependent libraries are in the > > WEB-INF/lib directory. The project itself is actually really small. > > > > > > -- > Regards - Ernesto Reinaldo Barreiro > Antilia Soft > http://antiliasoft.com/ <http://antiliasoft.com/antilia> >
