[jboss-user] [JBoss Seam] - Re: Using Seam Identity - What's the recommended approach?

Thank you both for your input. I had originally implemented my own login validation and am moving to JAAS so that I can take advantage of the role based security built into Seam. It is too bad about the hibernate validation though, I agree. In any case I'm running into another problem now which may be a jbpm bug Maybe someone's encountered it: code: loginProcess.jpdl.xml: . . . | <transition name="login-user" to="authenticateUser"> | <action expression="#{identity.login}" /> | </transition> | . . . error on return of "login-user" from a commandLink click: | 00:29:01,817 ERROR [GraphElement] action threw exception: couldn't evaluate expression '#{identity.login}' | org.jbpm.JbpmException: couldn't evaluate expression '#{identity.login}' | at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:38) | at org.jbpm.graph.def.Action.execute(Action.java:119) | . . . | Caused by: org.jbpm.jpdl.el.ELException: Unable to find a value for "login" in object of class "org.jboss.seam.security.RuleBasedIdentity" using operator "." | . . . | Caused by: org.jbpm.JbpmException: couldn't evaluate expression '#{identity.login}' | . . . | Caused by: org.jbpm.jpdl.el.ELException: Unable to find a value for "login" in object of class "org.jboss.seam.security.RuleBasedIdentity" using operator "." I found in another thread that a suggestion from GK to try overriding the login function - which I did -- it made no difference: @Name("org.jboss.seam.core.identity") | @Scope(ScopeType.SESSION) | @Intercept(InterceptionType.AFTER_RESTORE_VIEW) | public class OverrideIdentity extends RuleBasedIdentity | { | public String login() | { | return super.login(); | } | } Has anyone run into a similar problem? Thanks again for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027818#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...