RE: Is there any other way? DataProviders must hit the Db twice for (possible) large datasets

2008-11-26 Thread rgoodwin
Still is being disputed unfortunately :( https://issues.apache.org/jira/browse/WICKET-1784 For those who believe in the 1-query approach, ergo the DTO pattern, writing an alternative to the Wicket data provision using a DTO approach isn't a terrible hardship ... just annoying to be sprung with

Paging query relating to IDataProvider and Lucene search

2008-08-21 Thread rgoodwin
Hello, I'm trying to solve a variation on a standard problem regarding running searches for paged results and displaying paging links. Unfortunately for me, I cannot use the standard PagingNavigator / DataView / IDataProvider solution for this. Wicket's top-down approach to processing has a

Re: Paging query relating to IDataProvider and Lucene search

2008-08-21 Thread rgoodwin
Hi John, Thanks for replying. Would be a neat solution if only I could cache Hits. :( But in my desire to simplify the problem statement I omitted to mention that our data services tier runs in another cluster and converts Lucene hits/documents/fields to a collection of our in-house search