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

Expose features currently provided by ModelController via capabilities usable by extensions

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Beta12
    • None
    • Management
    • None

      A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it.

      Extensions may have a need to create an internal ModelControllerClient or to register notification handlers. Currently this is done by looking up the ModelController via its internal service name but:

      1) ModelController exposes methods that should not be available to extensions
      2) Accessing services should be via a capability.

      So, we need to expose capabilities for these functions.

              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: