Databases
StackOverflow2013
Postsdbo
POJava/Spring: Why won't Spring use the validator object I have configured?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava/Spring: Why won't Spring use the validator object I have configured?
    primarykey
    data
    text
    <p>I'm writing a web app with Java &amp; Spring 2.5.6 and using annotations for bean validation. I can get the <a href="http://wheelersoftware.com/articles/spring-bean-validation-framework.html" rel="nofollow noreferrer">basic annotation validation</a> working fine, and Spring will even call a custom Validator declared with @Validator on the target bean. But it always instantiates a brand new Validator object to do it. This is bad because the new validator has none of the injected dependencies it needs to run, and so it throws a null pointer exception on validate. I need one of two things and I don't know how to do either. </p> <ol> <li>Convince Spring to use the validator I have already configured.</li> <li>Convince Spring to honor the @Autowired annotations when it creates the new validator.</li> </ol> <p>The validator has the @Component annotation, like this.</p> <pre><code>@Component public class AccessCodeBeanValidator implements Validator { @Autowired private MessageSource messageSource; </code></pre> <p>Spring finds the validator in the component scan, injects the autowired dependencies, but then ignores it and creates a new one at validation time.</p> <p>The only thing that I can do at the moment is add a validator reference into the controller for each validator object and use that ref directly, instead of relying on the bean validation framework to call the validator for me. It looks like this.</p> <pre><code>// first validate via the annotations on the bean beanValidator.validate(accessCodeBean, result); // then validate using the specific validator class acbValidator.validate(accessCodeBean, result); if (result.hasErrors()) { </code></pre> <p>If anyone knows how to convince spring to use the existing validator, instead of creating a new one, or how to make it do the autowiring when it creates a new one, I'd love to know.</p> <p>Edit:<br> Here is the code that tells spring what validator to use for the bean.</p> <pre><code>@Validator(AccessCodeBeanValidator.class) public class AccessCodeBean { </code></pre> <p>It works, but is limited as described above.<br> And so, currently, I have the @Validator line commented out and instead I'm autowiring the validator to the controller like this.</p> <pre><code>@Resource(name="accessCodeBeanValidator") public void setAcbValidator(Validator acbValidator) { this.acbValidator = acbValidator; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGMK
    1. USGMK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. USjsight
      1. VTFavorite
    2. VO
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI suspect that you are just hitting a limitation of the module rather than a limitation of your usage. Can you show the code (annotation) that is attaching the validator to your controller?
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. USjsight
    2. COYes, I agree, its a strange omission. I'm just thinking that if it was their intent for these to be Spring Beans, that they would have given some different options for lookup them up (eg, bean name) instead of just lookup by class. I'm not 100% sure though, since I haven't tried looking at their code.
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. USjsight
    3. COI was thinking that might be the case, but it's a pretty large omission, don't you think? There are *many* cases where you need to validate against something in the database, or with a previously extant resource. I was hoping the developers had thought more carefully about it.
      singulars
      1. POJava/Spring: Why won't Spring use the validator object I have configured?
      1. USGMK
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload