We only allow one service per component today, which means that a single instance of an implementation cannot be configured to use different interfaces and policies via multiple component services. The issue with multiple interfaces can be addressed by promoting the component service multiple times with different interfaces, but this is a tad inelegant. The workaround for using different policies is to create multiple service components which use the same underlying resource as an implementation.

Investigate support for allowing multiple component services.