Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5107

Provide equivalent to RemotingConnectorInfo via org.jboss.as.network module; expose it via "org.wildfly.remoting.connector" capability

XMLWordPrintable

      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.

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: