Data Connector Validate Interface
Description
Environment
Activity
Scott Cantor November 11, 2015 at 3:12 PM
An example in the wiki would be good, if you have time.
Daniel Fisher November 11, 2015 at 5:16 AM
Made v2 parses failFast in r7980.
To make v2 parsers non-failFast, use the validatorRef attribute to reference a bean that is configured for non-failFast.
Daniel Fisher October 28, 2015 at 6:04 AM
Fixed in r7894.
Note that this commit changes the default behavior of the LDAP and RDBMS data connectors to non-fail fast for v2 configurations.
Scott Cantor October 27, 2015 at 1:48 PM
I would also. I think you can auto-inject an appropriately tailored Validator that way and just reuse the same mechanism.
I actually would suggest injecting a validator that still runs the validation but traps the exception, that way it still logs the problem at startup.
Daniel Fisher October 27, 2015 at 1:37 PM
Right. I'm still trying to decide if I want that switch on the Validator, on the DataConnector, or just in the schema. I'm leaning towards the schema.
Provide an interface to set on Data Connectors for custom implementations of validation.
Data Connectors should set their own default implementation.
Fail-fast can then be controlled by deployers.