The problem with this approach is it requires huge levels of duplication as each container needs to write their own adapter and error creation code. I'm particularly confused because it seems the solution already exists within commons-validator - ValidationResult(s). I would think a better approach would be for commons-validator to provide adapters for every validator to extract the field information from Field and pass it along to the actual validator. The process of creating messages should be left to the class that called validator.validate() to process ValidationResults and handle the errors in a container-specific way. This way, new containers that want to use commons-validator don't have to write their own monolithic adapter class but can use validators as they are. If commons-validator wants to separate a validator into a commons-validator adapter class and a actual validation class, that is fine, but there really isn't any need for that adapter to depend on a container.
If my premise is sound and the solution agreeable, I would be willing to do the leg work of writing container-independent adapters for each of the validators.
Don
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
