The way I understand it, this can be handled completely within SEAM. The @Valid annotation is specific to the Hibernate validator. However, the @IfInvalid is all SEAM. My variation on the idea is to change @IfInvalid as follows
| @Stateful | @Name("myController") | @Interceptors(SeamInterceptor.class) | public class MyController { | | // this entity will be set from form-1 | @In (value="user",create=true) | protected User user; | | // this entity will be set from form-2 | @In (value="address",create=true) | protected Address address; | | // this should validate user | @IfInvalid (name="user", outcome=Outcome.REDISPLAY) | public String pressButtonOneHandlingUsers() { | ... do something ... | } | | // this should validate user and address | @IfInvalid (name="address", outcome=Outcome.REDISPLAY) | public String pressButtonTwoHandlingAddress() { | ... do something ... | } | } | IfInvalid could also take a "names" parameter: @IfInvalid (names={"address","user"}, outcome= ...) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927159#3927159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927159 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user