I have an entity with a two-field unique constraint. Due to not being able to
write a validator that validates two fields of an entity at once (or am I wrong
here?), I ended up subclassing the EntityHome in order to run my object-level
validation before the superclass update() and persist() get
Is it possible to implement a hibernate validator with this functionality (run
a query to determine uniqueness)? It's not clear from looking at the hibernate
validator docs how i would inject a persistence context to use.
BTW, I got the above strategy to work, but had to change a few things to
>From reading the 1.2.1.GA docs, it appears that using JSF validators is
>deprecated in favor of using Hibernate validators.
Can a Hibernate validator also be a seam component similar to the above?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059997#4059997
We've got some simple CRUD operations that we're doing just by declaring an
entity-query and entity-home in components.xml, and building a list page and a
form page that bind to them. It works great, but one of our classes has a
unique constraint on one of the fields. Right now, if you enter d
Can anybody suggest the thinking behind choosing to use a page parameter vs.
@RequestParameter?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054503#4054503
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054503
__
