]
Tomaz Cerar commented on WFCORE-3435:
-------------------------------------
We should probably introduce something like CapabilityActivator.
Less breaking change would be having ServiceActivatorContext or implement some other
interface that would also expose capabilities or have serviceTarget return
CapabilityServiceTarget.
But both of this options would require that cast is done in ServiceActivator which could
case other issues.
Expose capability/requirements to deployments
---------------------------------------------
Key: WFCORE-3435
URL:
https://issues.jboss.org/browse/WFCORE-3435
Project: WildFly Core
Issue Type: Enhancement
Affects Versions: 3.0.9.Final
Reporter: Bob McWhirter
Assignee: Jason Greene
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 [~ctomc]