Subclassing Seam identity component

[mgrouch]

Are there any configurations required when I subclass Identity?
What are the best practices for extending Seam identity component?

Thanks

[shane.bryzak]

Can you provide more information describing your requirements?

[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.

[christian.bauer]

@Name("org.jboss.seam.security.identity")
@Scope(SESSION)
@BypassInterceptors
@Install(precedence=APPLICATION)
@Startup
public class MyIdentity extends Identity {}

[mgrouch]

Thanks. This helps

[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

[mgrouch]

Solved by extending RuleBasedIdentity

[shane.bryzak]

"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.