Hi, currently when using `CasAppender` it is difficult to troubleshoot issues the application has on startup.
When the application fails to start, likely something is going to log some hint about why the application failed to start. The problem is, that `CasAppender` tries to fetch the `MessageSanitizer` from the `ApplicationContext on every log. When something is logged after the application failed to start (likely some crucial information) that isn't possible. Instead a big long exception is printed that the application context isn't initialized yet. Could `CasAppender` do a) handle gracefully a uninitialized ApplicationContext or b) cache the `MessageSanitizier` so that at least these logs to debug application startup failure get logged? Currently when the application fails to start I manually have to switch from `CasAppender` to a regular appender to debug the issue. Regards Felix -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-dev/fc8414a3-d495-4beb-a325-f2f37a8e8991n%40apereo.org.
