You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gregor Kaczor (JIRA)" <ji...@apache.org> on 2011/08/13 11:06:27 UTC
[jira] [Updated] (SOLR-2710) SpellCheckResponse and TermsResponse
should implement Serializable
[ https://issues.apache.org/jira/browse/SOLR-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregor Kaczor updated SOLR-2710:
--------------------------------
Summary: SpellCheckResponse and TermsResponse should implement Serializable (was: SpellCheckResponse and TermsResponse sould implement Serializable)
> SpellCheckResponse and TermsResponse should implement Serializable
> ------------------------------------------------------------------
>
> Key: SOLR-2710
> URL: https://issues.apache.org/jira/browse/SOLR-2710
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.3, 4.0
> Reporter: Gregor Kaczor
> Priority: Minor
> Fix For: 3.4
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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 question is:
> Is there a good reason for SpellCheckResponse (and TermsResponse) not to
> implement Serializable? If used, both fields breake the serialisation of QueryResponse.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org