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

WildFly discovery subsystem registers capabilities using an ambiguous contract

XMLWordPrintable

      The discovery subsystem registers capabilities of the form RuntimeCapability<Void> with a service type of DiscoveryProvider.class with the model.

      However, during runtime it registers capabilities of the form RuntimeCapability<DiscoveryProvider> with the OperationContext using the same name.

      This violates the capability contract. Since the capability specified during resource registration is what defines the contract, and since non-trivial discovery provider implementations cannot reasonably register an implementation during the model phase without requiring runtime dependencies, we should prefer the former definition over the latter.

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

                Created:
                Updated:
                Resolved: