On 19/11/2025 23:28, Christopher Schultz wrote:
On 11/19/25 2:18 PM, Coty Sutherland wrote:
<snip/>
After writing all of that out, maybe this should be a separate tool
instead
of enhancements to configtest or we should incorporate some of the checks
into a pre-startup step in the boot process? Thoughts?
A separate tool does make sense to me if you already plan on the large
feature set shown above. I can only guess it will continue to metastasize.
While the size of the feature set does suggest a separate tool would be
better, that makes me think of the (very) old admin app where we had a
real problem keeping it in sync with changes to the components it was
meant to administer. That makes me think integration into the core
Tomcat code might be better.
That in turn got me thinking about how strict we want these checks to
be. We probably want three options: ignore, warn, refuse to start. And
probably want to set those per category - for some value of category.
Implementation-wise, something built on LifecycleListener?
Sorry I don't have concrete proposals and I'm unlikely to have much time
to help but in general I am in favour.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
