An infinispan-session-management resource configured with affinity=primary-owner or affinity=ranked requires routing=infinispan. However, if configured with routing=local, a deployment that uses this session-management provider will fail to deploy with missing services. This condition should be detected during server startup via capability constraints, rather than failing in this way (with confusing error messages).

To resolve this, we will create a new "org.wildfly.clustering.web.infinispan-routing-provider" capability provided only by the routing=infinispan resource, which will be required by the affinity=primary-owner and affinity=ranked resources.

We can leverage this new capability to more intelligently handle the condition where a distributable web application that uses legacy jboss-web.xml <replication-config/> is deployed to a non-ha profile - which currently only works when the distributable-web subsystem is not present.