[
https://issues.jboss.org/browse/WFLY-1917?page=com.atlassian.jira.plugin....
]
Jeff Mesnil resolved WFLY-1917.
-------------------------------
Resolution: Rejected
Preferred way to configure the messaging remote-connector is using outbound-socket-binding
that allows to define the address that the client must use to connect to the server.
Support socket-binding attribute "client-mapping" in
messaging subsystem
------------------------------------------------------------------------
Key: WFLY-1917
URL:
https://issues.jboss.org/browse/WFLY-1917
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JMS
Affects Versions: 8.0.0.Alpha4
Reporter: Justin Bertram
Assignee: Jeff Mesnil
The messaging subsystem doesn't take into account the "client-mapping"
attribute of the <socket-binding> when creating a <netty-connector>. This
forces the user to manually configure a <connector> to support the desired behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira