@BenjaminPerryRoss: I don't agree on this one, if I configure something wrong and the `cache.xml` can't be parsed altogether, I expect the member startup to halt right away and throw an exception so I know I did something wrong. If we continue with the startup and use the default restricted authorizer, it will be harder for our users later in time to debug what's wrong (_hey, why is this method being rejected if the authorizer I've provided is supposed to allow it??_ ). We also need to consider that the user executing queries (developer) might not the same one as the one configuring the cluster in the first place (operator). That said, throwing an exception and stopping the member from starting up is exactly what we do when a user makes a mistake configuring other aspects of the cache, like a `CacheListener`, a `CacheLoader`, a `CacheWriter`, etc..
[ Full content available at: https://github.com/apache/geode/pull/4161 ] This message was relayed via gitbox.apache.org for [email protected]
