[jboss-jira] [JBoss JIRA] Closed: (JBAS-6876) Configure binding interface via ServiceBindingManager

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-6876.
----------------------------------

    Resolution: Done


This is done for all services whose configuration is part of the AS codebase. JBM's config file comes from a JBM distribution, so it still uses ${jboss.bind.address}

> Configure binding interface via ServiceBindingManager
> -----------------------------------------------------
>
>                 Key: JBAS-6876
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6876
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Management services
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.1.0.GA
>
>
> The binding interface for services that open sockets should be coming from the ServiceBindingManager, same as the ports do. Currently most services use ${jboss.bind.address} to inject the address directly into the consuming service. But that precludes a management tool using SBM as a central configuration point for all address/port usage in the server (see JOPR-159). Currently it's mostly only useful for the ports; if admins wanted to use something other than ${jboss.bind.address} for a particular service they'd have to go elsewhere in the tool to configure that.
> This is just a matter of editing service config files; the SBM is already configured to return the correct values if asked.

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