Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6347 Port subsystem development enhancements from wildfly-clustering-common to wildfly-core
  3. WFCORE-6769

Port NaryServiceNameFactory logic from wildfly-clustering-common to ServiceNameFactory

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 24.0.0.Final
    • 24.0.0.Beta3
    • Management
    • None

      wildfly-clustering-common uses *naryServiceNameFactory interfaces to resolve a service descriptor to a ServiceName for use outside of management operations, e.g. for generating service names during DUP processing. In the absence of these methods, resolving a service descriptor to a ServiceName requires the same steps:

      Map.Entry<String, String[]> resolved = descriptor.resolve(...);
      return ServiceNameFactory.parseServiceName(resolved.getKey()).append(resolved.getValue());

      Since a service descriptor has a well-defined "cacheable" portion, moving this logic to methods within ServiceNameFactory is a natural fit.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: