Use application-level validation, in combination with manual flush - this way, the bean will be saved only if you explicitly ask for it via em.flush().
Thank you for your quick reply. Actually at present I already use your solution. But I think that it is a bit cumbersome. IMHO the best solution is usage a Hibernate bean level validator but as I can see Seam is not able to catch and process exception thrown by the validator and show global error message.
Hi ALL! Do you know other solution(s)?
i encountered the same problem. Hibernate offers bean-level validation. But this feature isnt properly integrated/supported in SEAM (especially with the frontend).
Therefore, we have to live with the application-level validation.