[jboss-jira] [JBoss JIRA] Commented: (JBREM-687) allow binding to 0.0.0.0
[ http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12351527 ]
Tom Elrod commented on JBREM-687:
----------------------------------
Have changed code so will allow binding to 0.0.0.0, but then server invoker will replace
the locator url's host (i.e. 0.0.0.0) with either host name or ip.
The change has *only* been made to CVS HEAD for now. The reason is going through code
freeze for 2.2.0.beta1 release (which is on remoting_2_x branch). Once 2.0.0.beta1 is
released, can migrate changes from HEAD to remoting_2_x branch for beta2 release.
Following are file changes (in HEAD)
org.jboss.remoting.InvokerLocator (revision 1.23)
org.jboss.remoting.ServerInvoker (revision 1.62)
org.jboss.test.remoting.binding.BindingTestCase (new)
allow binding to 0.0.0.0
------------------------
Key: JBREM-687
URL: http://jira.jboss.com/jira/browse/JBREM-687
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta2 (Boon)
Need to be able to really bind to 0.0.0.0. Currently, remoting will swap out 0.0.0.0
with local host name or address. Although this is about only way to be able to provide an
invoker locator url that can be used by anyone else externally, means that only one
network interface can ever be used. For things such as JNDI, may want to use all
interfaces and need to add back in ability to do 0.0.0.0 binding.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira