]
Brian Stansberry updated WFCORE-5107:
-------------------------------------
Summary: Provide equivalent to RemotingConnectorInfo via org.jboss.as.network module;
expose it via "org.wildfly.remoting.connector" capability (was: Provide
equivalent to RemotingConnectorInfo via org.jboss.as.network module; expose it via
"org.wildfly.remoting.connector")
Provide equivalent to RemotingConnectorInfo via org.jboss.as.network
module; expose it via "org.wildfly.remoting.connector" capability
--------------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-5107
URL:
https://issues.redhat.com/browse/WFCORE-5107
Project: WildFly Core
Issue Type: Enhancement
Components: Remoting
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
Get rid of the need for other subsystems to use RemotingConnectorBindingInfoService /
RemotingConnectorInfo.
RemotingConnectorInfo is a trivial data object, the equivalent of which could be a type
in the org.jboss.as.network module. RemotingConnectorBindingInfoService is fine; it just
exposes the data object, but the existing "org.wildfly.remoting.connector"
should expose the new type and any public service name from
RemotingConnectorBindingInfoService should be deprecated.
For compatibility RemotingConnectorInfo can wrap the new type and
RemotingConnectorBindingInfoService can take a consumer for both the new type and
RemotingConnectorInfo.