Complete the support for capabilities for the remaining Remoting resources -------------------------------------------------------------------------- Key: WFCORE-5055 URL: https://issues.redhat.com/browse/WFCORE-5055 Project: WildFly Core Issue Type: Enhancement Components: Remoting Affects Versions: 13.0.0.Beta1 Reporter: Richard Achmatowicz Assignee: Flavia Rainone Priority: Major There are some Remoting resources which still use legacy service name generation for installing services (e.g. Connector) which means that any subsystems which depend on these resources cannot establish capability references to the capabilities they depend on. For example: {noformat} /** The name of the remoting service */ public static final ServiceName REMOTING_BASE = ServiceName.JBOSS.append("remoting"); /** The name of the endpoint service installed by the remoting subsystem. */ public static final ServiceName SUBSYSTEM_ENDPOINT = REMOTING_ENDPOINT_CAPABILITY.getCapabilityServiceName(Endpoint.class);//REMOTING_BASE.append("endpoint", "subsystem"); /** The base name of the connector services */ private static final ServiceName CONNECTOR_BASE = REMOTING_BASE.append("connector"); /** The base name of the stream server services */ private static final ServiceName SERVER_BASE = REMOTING_BASE.append("server"); public static final ServiceName HTTP_LISTENER_REGISTRY = HTTP_LISTENER_REGISTRY_CAPABILITY.getCapabilityServiceName(ListenerRegistry.class);{noformat} It would be nice to provide capability-based installation for connector and stream services as well.