lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-1407) Refactor Searchable to not have RMI Remote dependency
Date Thu, 11 Jun 2009 10:43:07 GMT


Shai Erera commented on LUCENE-1407:

Hmm ... maybe that won't be that simple. As part of LUCENE-1630, I'm deprecating Searchable,
and the plan is to stick with just Searcher. Now, RemoteSearchable today implements Searchalbe
(and by inheritance java.rmi.Remote) as well as extend UnicastRemoteObject.

After refactoring, it will need to extend both Searcher and UnicastRemoteObject. Unless we
make Searcher extend UnicastRemoteObject, but that will bring the RMI stuff back into core.

Anybody got an idea how we can work around that besides keeping Searchable, or have Searcher
extend UnicastRemoteObject?

> Refactor Searchable to not have RMI Remote dependency
> -----------------------------------------------------
>                 Key: LUCENE-1407
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 2.9
> Per
> We should refactor Searchable slightly so that it doesn't extend the java.rmi.Remote
marker interface.  I believe the same could be achieved by just marking the RemoteSearchable
and refactoring the RMI implementation out of core and into a contrib.
> If we do this, we should deprecate/denote it for 2.9 and then move it for 3.0

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:
For additional commands, e-mail:

View raw message