[
https://issues.apache.org/jira/browse/LUCENE-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718472#action_12718472
]
Shai Erera commented on LUCENE-1407:
------------------------------------
>From UnicastRemoteObject's documentation:
{quote}
If the remote object is exported using the exportObject(Remote)
UnicastRemoteObject.exportObject(Remote) method, a stub class (typically
pregenerated from the remote object's class using the rmic tool) is loaded and
an instance of that stub class is constructed as follows.
* A "root class" is determined as follows: if the remote object's class
directly implements an interface that extends Remote, then the remote object's
class is the root class; otherwise, the root class is the most derived
superclass of the remote object's class that directly implements an interface
that extends Remote.
{quote}
Naming.lookup only succeeds when Searchable extends Remote, and
RemoteSearchable implements Searchable. In fact, the type returned by lookup()
is Searchable, not even RemoteSearchable.
I guess we can solve it by having RemoteSearchable implement a Remoteable
interface which extends Remote .. but that's just spooky. For now I left the
code in LUCENE-1630 as-is in that area.
> Refactor Searchable to not have RMI Remote dependency
> -----------------------------------------------------
>
> Key: LUCENE-1407
> URL: https://issues.apache.org/jira/browse/LUCENE-1407
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Priority: Minor
> Fix For: 2.9
>
>
> Per http://lucene.markmail.org/message/fu34tuomnqejchfj?q=RemoteSearchable
> 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: [email protected]
For additional commands, e-mail: [email protected]
