Yes it needs to be defined in the configuration class / xml. The described behavior points that both validator classes are in the Spring Context active in your case now. (The fixed one and the broken from Spring).

I would check where the current spring validator is coming from. Either from a imported namespace or some auto magic. Usually (in spring-data) the validator isn’t configured by default. I would assume the same for here now for the XML configuration. –> Means I think you have somewhere in XML the spring validator too. Does this make sense?

The question is also not about the spring core version but Spring Data / Mongo version. Nevertheless my patch till now didn’t made it into the lib, I can say for sure that spring-data-mongodb is affected until version 1.9.1.RELEASE.

Seems that posts in this website do not allow XML code… :-(. In any case, should not FixedMongoValidation be somehow specified in the configuration class? Thanks!

I am having the same issue and followed your same steps. However, both my custom validation listener and Spring’s are being executed.

I am using Spring 3.2.9 and XML configuration instead, and tried the following configurations:

Any help fixing this issue would be more than appreciated 😉