[WICKET-6382] @Autowired in Validator doesn't work with PropertyValidator

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 8.0.0-M6
• Component/s: wicket-bean-validation, wicket-spring
• Assignee: Sven Meier
• Reporter: Kamil
• Created: 29/May/17 12:06
• Updated: 09/Jun/17 09:26
• Resolved: 08/Jun/17 19:14

Description

I have a generic validator:

@Component
public class UniqueFieldValidator implements ConstraintValidator<UniqueFieldValidator.UniqueField, String> {

    private AbstractEntityRepository<?,?> repository;

    private String fieldName;

    @Autowired
    private ApplicationContext applicationContext;

    @Target({ElementType.METHOD, ElementType.FIELD})
    @Retention(RetentionPolicy.RUNTIME)
    @Constraint(validatedBy = UniqueFieldValidator.class)
    @Documented
    public @interface UniqueField {

        String fieldName();

        Class<? extends AbstractEntityRepository<?,?>> repository();

        String message() default "field.not.unique";

        Class<?>[] groups() default {};

        Class<? extends Payload>[] payload() default {};
    }

    @Override
    public void initialize(UniqueField uniqueField) {
        this.repository = applicationContext.getBean(uniqueField.repository());
        fieldName = uniqueField.fieldName();
    }

    @Override
    public boolean isValid(String value, ConstraintValidatorContext ctx) {
        if(isBlank(value)){
            return true;
        }
        Optional<?> o = repository.getOneByUniqueField(fieldName, value);
        return isFalse(o.isPresent());
    }
}

It works perfectly fine with SpringMVC Controllers, but when using Wicket's

new PropertyValidator<>()

field "repository" is null

Can you please take care that fields in Validators gets injected as well?