I've noticed this while reviewing the 
`queryServiceWithUserDefinedAuthorizerCanBeLoadedFromXml` test above, whenever 
there's an error the log contains something like `[error 2019/10/25 
14:34:12.701 IST <main> tid=0x1] Exception while updating 
MethodInvocationAuthorizer: No MethodInvocationAuthorizer class found with name 
org.apache.geode.cache.util.TestMethodAuthorizer. The authorizer was not 
updated. Reason: java.lang.ClassNotFoundException: 
org.apache.geode.cache.util.TestMethodAuthorizer`.
The above is not "visible enough" from an user perspective I think, shouldn't 
we entirely abort the startup if there's an exception parsing the XML file?, 
would it make sense to add the proper stack trace to the error logged as well?.

[ Full content available at: https://github.com/apache/geode/pull/4161 ]
This message was relayed via gitbox.apache.org for 
[email protected]

Reply via email to