Possibly, but it is just metadata that can be used to capture resource
usage. In this particular usecase, the server's interfaces due dictate
what values other jca services are listening on. In the future if we get
into n-tier deployments that would not be the case, but then you still
need an inventory of what the point to point connection endpoints are.
The admin needs some way to define tier interfaces, and configure the
connections between them. I would think we would do this via the
interfaces and socket-binding-group metadata.
On 7/19/11 6:32 AM, Jaikiran Pai wrote:
I might be wrong, but isn't the socket-binding elements within
the
standalone/domain xml meant to be only for the sockets opened within the
JBoss AS process and not for sockets opened by external processes (like
databases)?
-Jaikiran