This content has been marked as final.
Show 7 replies
-
1. Re: Subclassing Seam identity component
shane.bryzak Jul 25, 2007 1:07 PM (in response to mgrouch)Can you provide more information describing your requirements?
-
2. Re: Subclassing Seam identity component
mgrouch Jul 25, 2007 1:11 PM (in response to mgrouch)Upon user login we need to load user preferences, accounts, permissions etc (user specific information). This logically should be Session scope.
I though more proper way of doing it is to create a bean which
extends identity. -
3. Re: Subclassing Seam identity component
christian.bauer Jul 25, 2007 1:30 PM (in response to mgrouch)@Name("org.jboss.seam.security.identity") @Scope(SESSION) @BypassInterceptors @Install(precedence=APPLICATION) @Startup public class MyIdentity extends Identity {}
-
4. Re: Subclassing Seam identity component
mgrouch Jul 25, 2007 1:45 PM (in response to mgrouch)Thanks. This helps
-
5. Re: Subclassing Seam identity component
mgrouch Jul 25, 2007 4:02 PM (in response to mgrouch)Is there more to the configuration?
I get exception on startup[java] Caused by: java.lang.IllegalArgumentException: no such setter method: com.test.portal.web.common.CurrentUserBean.securityR
ules
[java] at org.jboss.seam.util.Reflections.getSetterMethod(Reflections.java:220)
[java] at org.jboss.seam.Component.initInitializers(Component.java:431)
[java] at org.jboss.seam.Component.<init>(Component.java:257)
[java] at org.jboss.seam.Component.<init>(Component.java:207)
[java] at org.jboss.seam.init.Initialization.addComponent(Initialization.java:894)
[java] ... 139 more -
6. Re: Subclassing Seam identity component
mgrouch Jul 25, 2007 4:30 PM (in response to mgrouch)Solved by extending RuleBasedIdentity
-
7. Re: Subclassing Seam identity component
shane.bryzak Jul 25, 2007 5:58 PM (in response to mgrouch)"mgrouch" wrote:
Upon user login we need to load user preferences, accounts, permissions etc (user specific information). This logically should be Session scope.
I though more proper way of doing it is to create a bean which
extends identity.
I recommend that you do this kind of stuff in your authenticator class, rather than extending Identity to do it.