May be annotating validation constraints on field level ist not the best solution, but by now it's explicitly mentioned as a possibility without other indication of restrictions in hibernate validator doc. But obviously this method is not safe with hibernate proxy instances as it is demonstrated be test case attached to original issue (http://opensource.atlassian.com/projects/hibernate/secure/attachment/14092/testcase.tar.gz). My first patch was a quick fix that worked for our case and a agree once again that it may have some side effects as it changes the semantic of field annotation. but my second solution (http://opensource.atlassian.com/projects/hibernate/secure/attachment/14091/proxy-fix.patch) leaves every thing as it is and just handles proxy instances differently and produce a more correct validation result than in current version.
I hope that you can do something with my ideas or a least document this limitation when using field annotation.
Are there any news regarding this issue? I'm still facing several false validation alerts while using lazy loaded entities with internal Javassist proxies.
No since I submitted the proxy-fix.patch nothing I didn't hear anything from Emmanuel. Perhaphs he gets not infomed about changes on this subtask as the main issue has been closed (I don't exacly know how Jira handles such cases). In any case I'm successfully using the posted patch in a project that now in production.
May be closed as I opened a new issue.
Move issues into the legacy component since they are pre 3.x which is based on a different codebase