Currently, CapabilityServiceTarget.addService() returns a ServiceBuilder<?> which lacks the ability to register capability requirements and provide capability service values.

Now that the ServiceTarget exposed by the OperationContext supports the addService() method, we can overload CapabilityServiceTarget.addService() to return a CapabilityServiceBuilder<?> which lets consumers do all of the above.

This effectively prevents users from having to specify the capability twice when creating a service.

Other overload candidates include:

• ServiceTarget.add/removeListener(...)
• ServiceBuilder.addListener(...)

Overloading ServiceTarget.subTarget() is not likely appropriate for the OperationContext.