jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: [jira] Resolved: (JCRRMI-13) Enhancement to get RMI through firewalls
Date Fri, 03 Apr 2009 14:19:55 GMT
I updated jackrabbit trunk to try to look at the code changes and  
didn't see anything updated. I then blew away trunk and checked out  
jackrabbit/trunk. Still, these changes weren't there. I then looked at  
the commit email and noticed the changes actually went to jackrabbit/ 
commons/jcr-rmi.

I apologize if I missed a discussion on this, but how will commons/jcr- 
rmi be included if jcr-rmi is already a subproject of trunk or the 1.5  
branch?  If jcr-rmi is going to appear in trunk shouldn't it be an  
external link to commons/jcr-rmi?

Ralph

On Apr 3, 2009, at 4:18 AM, Jukka Zitting (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/JCRRMI-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

>  ]
>
> Jukka Zitting resolved JCRRMI-13.
> ---------------------------------
>
>       Resolution: Fixed
>    Fix Version/s: 2.0
>         Assignee: Jukka Zitting
>
> Implemented in revision 761613.
>
> I made the port number an attribute of the ServerAdapterFactory  
> class, so you can easily set it in Java code when instantiating the  
> server:
>
> {code}
> ServerAdapterFactory factory = new ServerAdapterFactory();
> factory.setPortNumber(...)
> RemoteRepository remote = factory.getRemoteRepository(repository);
> {code}
>
> If the port number is not explicitly set, then it is set to the  
> value of the proposed org.apache.jackrabbit.rmi.port system  
> property. If that property is not set, then the default value 0 (for  
> a random port) is used.
>
>> Enhancement to get RMI through firewalls
>> ----------------------------------------
>>
>>                Key: JCRRMI-13
>>                URL: https://issues.apache.org/jira/browse/JCRRMI-13
>>            Project: Jackrabbit JCR-RMI
>>         Issue Type: Improvement
>>        Environment: RHEL Linux 5.0
>>           Reporter: Tony Richardson
>>           Assignee: Jukka Zitting
>>            Fix For: 2.0
>>
>>
>> It is difficult to get RMI through a firewall with the current  
>> implementation of org.apache.jackrabbit.rmi.server.ServerObject. As  
>> it selects a random port for RMI execution. This issue can be  
>> resolved by adding a system property and modifying the default  
>> constructor as shown below.
>>  private static Integer bindPort =  
>> Integer.getInteger("org.apache.jackrabbit.rmi.port", new Integer(0));
>>    /**
>>     * Creates a basic server adapter that uses the given factory
>>     * to create new adapters.
>>     *
>>     * @param factory remote adapter factory
>>     * @throws RemoteException on RMI errors
>>     */
>>    protected ServerObject(RemoteAdapterFactory factory)
>>            throws RemoteException {
>>        super(bindPort.intValue());
>>        this.factory = factory;
>>    }
>
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>


Mime
View raw message