I opened a JIRA issue for : https://issues.apache.org/jira/browse/SOLR-2710
You are right about LoadableDetachableModel, i had a look at it. It is
an option but this solution would put unnecessary load on the index
servers and network which i would like to avoid. After all local
serialisation is faster on small resultsets then requesting it over
network again.
On 08/13/2011 06:47 AM, Ryan McKinley wrote:
I don't think there is a reason -- maybe open a JIRA issue for this.
For wicket, i would recommend looking at LoadableDetachableModel this
will make the query once for each request and avoid serializing the
results
On Fri, Aug 12, 2011 at 4:27 PM, Gregor Kaczor<[email protected]> wrote:
I am using apache wicket and apache solr.
In wicket i am passing QueryResponse to several classes which worked fine
until I started using SpellChecking.
Wicket is serializing objects in order to store them between requests.
QueryResponse implements Serializable but SpellCheckResponse which is a
member field of QueryResponse does not. This leads to Exceptions.
My questions are:
Is there a good reason for SpellCheckResponse (and TermsResponse) not to
implement Serializable?
Kind Regards
Gregor
--
How to find files on the Internet? FindFiles.net!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
How to find files on the Internet? FindFiles.net <http://findfiles.net>!
