Current, when adding a session management resource in the distributable-web subsystem via:

/subsystem=distributable-web/infinispan-session-management=foo:add(cache-container=web)

... the distributable-web subsystem auto-generates an affinity=primary-owner child resource.

While the resource is valid for HA profiles, this command fails for non-HA profile whose default routing=local resource is not compatible with affinity=primary-owner.

To fix this, we should dynamically auto-create an appropriate affinity=* resource depending on either the existing routing=* resource, or based on the capability of the backing cache configuration, i.e. if the backing cache configuration is local, use affinity=local, if the backing cache configuration is clustered, use affinity=primary-owner - although, this technically does not mean that the correct routing=* resource exists, but would more closely predict the intent of the user.