[
https://issues.apache.org/jira/browse/LUCENE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652921#action_12652921
]
Jason Rutherglen commented on LUCENE-1473:
------------------------------------------
Mark: "There will be complaints no matter what. GWT tried getting around people
having to implement Serializable by providing an interface with fewer promises:
isSerizable. Many complained right away, as they had other classes that perhaps
they where making Serializable simply for Apache XMLRpc or something. So now
you can use either Serializable or isSerialiazble.
Personally, I think its fine to do as we are. I'm not against supporting more
though. "
Externalizable and Serializable work interchangeably, a nice feature of Java.
For classes that no one submits an Externalizable patch for, the
serialVersionUID needs to be added. For ones that implement Externalizable,
there is slightly more work, but not something someone with a year of Java
experience can't maintain.
> Implement Externalizable in main top level searcher classes
> -----------------------------------------------------------
>
> Key: LUCENE-1473
> URL: https://issues.apache.org/jira/browse/LUCENE-1473
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Minor
> Attachments: LUCENE-1473.patch
>
>
> To maintain serialization compatibility between Lucene versions, major
> classes can implement Externalizable. This will make Serialization faster
> due to no reflection required and maintain backwards compatibility.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
