[
https://issues.apache.org/jira/browse/JCRRMI-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696192#action_12696192
]
Felix Meschberger commented on JCRRMI-13:
-----------------------------------------
System properties make me shiver in modular application environments such as
servlet containers or OSGi framework.
Do we really need support for the system property ?
Can we also have the portnumber as an argument to a new constructor instead of
just a setter (setter is still good, of course) ?
> 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.
