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

Complete the support for capabilities for the remaining Remoting resources

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • 13.0.0.Beta1
    • Remoting
    • None

    Description

      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:

      /** 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);

      It would be nice to provide capability-based installation for connector and stream services as well. 

      Attachments

        Activity

          People

            flaviarnn Flavia Rainone
            rachmato@redhat.com Richard Achmatowicz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: