Álvaro, thanks for your comment. Yes, you can work around the issue in the way you describe but you should be aware that this potentially causes lots of entities to be loaded from the database upon validation of a bean which has non-loaded lazy references to other entities.

So to be on the safe side, I recommend you make sure to have a consistent set up of JPA API and implementation and use the default traversable resolver (or you implement your own provider which works with your kind of JPA set up but doesn't fetch lazy references).