I think I may have resolved the issue although I still feel it's a bit hacky.
On the data provider implementation, I set a searchString property every time a new search is entered and then clear out the cached list and reload new data (slight optimization - don't refresh is string is same as old one). And from within the onClick() method on the form, I call dataProvider.setSearchString(<get model value>). Although this works, is this the right way of doing things? I haven't worked with Wicket long enough to understand the memory profile when using such data sets but can I optimize this any? Thanks again! cbchhaya wrote: > > Hi, > > That's right. How do I replace the dataProvider? It doesn't have an ID so > I can't use replaceWith... Any suggestions? > > Thanks! > > > Newgro wrote: >> >> I don't see the complete process, but if i'm not completely wrong you is >> creating the DataProvider instance twice. Once in constructor and once >> in the AjaxButton.onSubmit method. But you is not assign this new >> instance to the dataview. Hit me if i'm wrong. >> >> Cheers >> Per >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- View this message in context: http://www.nabble.com/Refreshing-DataView-with-new-dataset-tp21650528p21654195.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
