It basically just adds a layer of indirection. The ServiceBindingManager
would get its values from jboss.bind.address (unless changed by the
user.) Bootstrap would still need to set parse cmd line args and set
properties as before.
Andrew Lee Rubinger wrote:
How does this relate to Main's handling of "-b" and the
responsibility
of Bootstrap to set "jboss.bind.address"? I've been working under the
assumption that all system properties currently set by the server must
be continued for backwards-compatibility sake.
S,
ALR
Brian Stansberry wrote:
> I think 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.[1] 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.
>
> Thoughts?
>
> [1] See my comment on
https://jira.jboss.org/jira/browse/JOPR-159
>
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com