jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-781) RMI: Allow custom socket factories
Date Mon, 16 Apr 2007 21:47:15 GMT

    [ https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489242

Ate Douma commented on JCR-781:

To make a little more clear what seems to be the problem:

The new "default" behavior of  new ServerAdapterFactory().getRemoteRepository(repo) without
explicitely configuring a custom RMIClientSocketFactory and RMIServerSocketFactory leads to
different (and for us failing) behavior compared to the earlier implicit setup where you couldn't
specify custom socket factories.
And the difference comes from how the UnicastRemoteObject parent of org.apache.jackrabbit.rmi.server.ServerObject
 creates the Remote object.
Implicit custom socket factories: 
  return exportObject(obj, new UnicastServerRef(port));
Explicit custom socket factories:
  return exportObject(obj, new UnicastServerRef2(port, csf, ssf))


> RMI: Allow custom socket factories
> ----------------------------------
>                 Key: JCR-781
>                 URL: https://issues.apache.org/jira/browse/JCR-781
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: rmi
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.3
> The current JCR-RMI server classes always use the default RMI socket factory. Provide
a mechanism for specifying a custom socket factory.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message