"[EMAIL PROTECTED]" wrote :
| No, you are completely correct. Don't use s:validate/s:validateAll in your
search form, and don't try to persist the entity you are using to hold your
search data and it won't be validated.
|
Oh, I was using the template="edit.xhtm" and it has s:validateAll, f
"jazir1979" wrote : From my understanding, you need s:validate to trigger
hibernate validator at the JSF level. Otherwise, the validations only trigger
when you try to persist an entity? I could be wrong, however.
No, you are completely correct. Don't use s:validate/s:validateAll in your
sear
date range point well-taken
"jazir1979" wrote :
| Another thing I'd point out is that using an entity for search values only
works in the simplest of cases - you can't easily do date ranges, for example.
|
| "menashe" wrote : it is not s:validate it is hibernate validator that is
the pro
>From my understanding, you need s:validate to trigger hibernate validator at
>the JSF level. Otherwise, the validations only trigger when you try to
>persist an entity? I could be wrong, however.
Another thing I'd point out is that using an entity for search values only
works in the simples
it is not s:validate it is hibernate validator that is the problem
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114052#4114052
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114052
I don't use seam-gen, and my project doesn't use entity fields to carry across
search values... but I wonder, why would you even have your search fields
inside s:validate in your UI?
"menashe" wrote : After looking at the seam examples and seamgen code on how
the search is done. It seams to me
