Re: Problem with paged datatable and model

2015-08-20 Thread Sven Meier
Hi Ilia, multiple calls to #size() were discussed in this issue already: https://issues.apache.org/jira/browse/WICKET-1766 Sven On 20.08.2015 01:40, Илья Нарыжный wrote: Sven, That's actually done:) I know this problem. The problem for this particular case is in another place: ajax pagi

Re: Problem with paged datatable and model

2015-08-19 Thread Илья Нарыжный
Sven, That's actually done:) I know this problem. The problem for this particular case is in another place: ajax paging links needs to know size of IDataProvider's data. And actually wicket AjaxPagingLink invokes prover and corresponding model for that. So, I mean, all ways to optimize bahaviour l

Re: Problem with paged datatable and model

2015-08-19 Thread Sven Meier
Hi, > in complex apps enable and visiblity can be linked with security settings and so on this is why you should override #onConfigure() and call #setEnabled() and #setVisible() from there. Have fun Sven On 19.08.2015 06:19, Илья Нарыжный wrote: Sven, Thanks! In my case IDataProvider pr

Re: Problem with paged datatable and model

2015-08-18 Thread Илья Нарыжный
Sven, Thanks! In my case IDataProvider provides data from DB. And these options leads to double query to DB... And that's a little bit redundant... DataProvider: https://github.com/OrienteerDW/wicket-orientdb/blob/master/wicket-orientdb/src/main/java/ru/ydn/wicket/wicketorientdb/model/OQueryDataPr

Re: Problem with paged datatable and model

2015-08-16 Thread Sven Meier
Hi, actually this is a known case where you have to call #detach() on your model by yourself: onClick() { service.delete(rowModel.getObject()); // let model reload the items tableModel.detach(); } Alternatively you can change IDataProvider#model() to provide a model, which c