[ https://issues.redhat.com/browse/WFCORE-5107?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5107: ------------------------------------- Description: 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" capability 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. was: 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. -- This message was sent by Atlassian Jira (v7.13.8#713008)