There are some glitches in the way the ConnectionFactoryValidator implements the component interface because the LDAP connector actually modifies the validator during its own initiialization, so there’s a cycle you can’t break. The only reason it’s not breaking is that the code apparently isn’t actually invoking initialize most of the time and the “do” method doesn’t check that either.
It appears to me we probably need this to avoid the post-init mutation by exposing the fail-fast semantic as a parameter to the validate method itself.
Environment
None
Activity
Daniel Fisher
December 18, 2022 at 10:34 PM
Fixed in
LDAP and RDBMS validators no longer extend AbstractInitializableComponent
There are some glitches in the way the ConnectionFactoryValidator implements the component interface because the LDAP connector actually modifies the validator during its own initiialization, so there’s a cycle you can’t break. The only reason it’s not breaking is that the code apparently isn’t actually invoking initialize most of the time and the “do” method doesn’t check that either.
It appears to me we probably need this to avoid the post-init mutation by exposing the fail-fast semantic as a parameter to the validate method itself.