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

Expose capability/requirements to deployments

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 3.0.9.Final
    • Management
    • None

      For WildFly Swarm, we use a fair amount of ServiceActivators in deployments.

      Moving to WF11, we have seen some of our dependencies on Service<T>, such as NamingService.SERVICE_NAME result in deprecation warnings suggesting we move to using CAPABILITY_NAME. From within a ServiceActivator, within a deployment, this appears to not be a possibility.

      Filed per tomazcerar

              jmesnil1@redhat.com Jeff Mesnil
              bmcwhirt@redhat.com Bob McWhirter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: