[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-02-18 Thread boevink
UserList.xhtml as generated: | !DOCTYPE composition PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN | http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; | | | ui:composition xmlns=http://www.w3.org/1999/xhtml; |

[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-02-15 Thread boevink
Strange because I am using the display template I'm using the templates and views as generated by seam-gen and can't get it working View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4129569#4129569 Reply to the post :

[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-02-15 Thread stu2
Hmm, that is odd. Can you post the relevant portions of your xhtml and also your template? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4129696#4129696 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4129696

[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-02-13 Thread boevink
I've exactly the same problem. The default display decorator is used as generated by seam-gen. A userLsit (entityQuery) is also generated by seam-gen. I would like to search for a user by e-mail address, but validation is performed (must be a well-formed email address) since there exists an

[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-02-13 Thread stu2
Pete was exactly right in my case. I was using the edit.xhtml template that did validation. For search fields you shouldn't use your edit template. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4129230#4129230 Reply to the post :

[jboss-user] [JBoss Seam] - Re: Bypassing validations when using EntityQuery with exampl

2008-01-20 Thread [EMAIL PROTECTED]
anonymous wrote : I'm not using s:validate or s:validateAll, which I thought was what triggered this behavior. Any suggestions? Is this how it is supposed to be? No, its not. Validation is triggered in two places with Seam. (1) s:validate(All), (2) by hibernate when persisting an entity. Are