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 results objects. No Lucene objects are sent back to the UI server. These search result objects are a bit like DTOs, but not in the pre-EJB3 sense. They're really just to standardise our search results architecture, as certain search result subclasses actually do db hits. So we want everything unified for the web app. This is why I made reference in the Wicket Jira ticket WICKET-1784 to the Transfer Object pattern, as solving this problem with respect to DTOs (instead of just Lucene) would solve for all interaction with legacy systems using DTOs, me thinks. (DTOs get a bad name these days now that entities are detachable, but I believe they still have their uses, e.g. for abstracting) Thanks again, and very open to simple solutions. Not keen on re-inventing the Wicket wheel. -- View this message in context: http://www.nabble.com/Paging-query-relating-to-IDataProvider-and-Lucene-search-tp19083164p19094471.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]
