juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Closed: (JUDDI-386) juddi's RMI InquiryService/PublishService needs a way of setting the random port that is being opened up.
Date Tue, 04 May 2010 21:27:04 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kurt T Stam closed JUDDI-386.
-----------------------------

    Resolution: Fixed

Added code and test to allow specifying the RMI port. Note that registering to JNDI running
in tomcat does not work. For that you can add config to the web.xml.

> juddi's RMI InquiryService/PublishService needs a way of setting the random port that
is being opened up.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-386
>                 URL: https://issues.apache.org/jira/browse/JUDDI-386
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.0.2
>            Reporter: Tom Cunningham
>            Assignee: Tom Cunningham
>             Fix For: 3.0.2
>
>
> juddi's RMI InquiryService/PublishService needs a way of setting the random port that
is being opened up.      The random port is a problem for users behind a firewall.    We should
be doing something like : 
> super(<port number>) 
> rather than 
> super()

-- 
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