Cache configurations are currently validated against the GlobalConfiguration via ConfigurationChildBuilder#validate, however there are scenarios where this isn't sufficient and it's necessary for a configuration to be validated against the current global state of the CacheManager. For example, it's not possible to validate a configuration against the JGroups stack configuration as users can provide a JGroups stack file that's not parsed by Infinispan.

The current solution is for Caches to be started, with this validation performed on startup, resulting in caches transitioning to the FAILED state. This can cause problems for applications tracking the state of cache creation, such as the Operator.

A better solution would be to fail-fast by providing an additional mechanism that allows a configuration to be validated against the current state of the CacheManager before cache creation.