[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1022) Fix misleading javadoc in InvokerLocator

Ron Sigal (JIRA) jira-events at lists.jboss.org
Thu Aug 7 19:02:49 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBREM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1022.
----------------------------

    Resolution: Done


Change applied to 2.2 and 2.x branches.

> Fix misleading javadoc in InvokerLocator
> ----------------------------------------
>
>                 Key: JBREM-1022
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1022
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.GA (Pinto), 2.2.2.SP9
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>            Priority: Minor
>             Fix For: 2.4.0.SP1, 2.2.2.SP10
>
>
> The following note in the org.jboss.remoting.InvokerLocator javadoc is incorrect:
>    * NOTE: the hostname will automatically be resolved to the outside IP address of the local machine
>    * if <tt>localhost</tt> or <tt>127.0.0.1</tt> is used as the hostname in the URI.  If it cannot be
>    * determined or resolved, it will use what was passed.
>    
> In fact, it is only a missing hostname (and 0.0.0.0 in the special case that the system property "jboss.bind.address" is set) that will be replaced.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-remoting-issues mailing list