[jira] Issue Comment Edited: (JUDDI-386) juddi's RMI InquiryService/PublishService needs a way of setting the random port that is being opened up.

["Kurt T Stam (JIRA)" <ju...@ws.apache.org>]

    [ https://issues.apache.org/jira/browse/JUDDI-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864012#action_12864012 ] 

Kurt T Stam edited comment on JUDDI-386 at 5/4/10 5:27 PM:
-----------------------------------------------------------

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

      was (Author: kurtstam):
    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.