Comments on: Extending Seam Components http://blog.laststation.net/2007/10/14/extending-seam-components/ Tue, 03 Nov 2009 04:24:26 +0000 http://wordpress.com/ hourly 1 By: laststation.net » Blog Archive » Generic JSF Converter for Seam http://blog.laststation.net/2007/10/14/extending-seam-components/#comment-35 laststation.net » Blog Archive » Generic JSF Converter for Seam Sun, 16 Nov 2008 18:46:09 +0000 http://laststation.net/2007/10/14/extending-seam-components/#comment-35 [...] is quite straightforward, following the same principles as I’ve shown in the post Extending Seam components. It’s important to keep this component stateless (or at least bound them to EVENT scope) to [...] [...] is quite straightforward, following the same principles as I’ve shown in the post Extending Seam components. It’s important to keep this component stateless (or at least bound them to EVENT scope) to [...]

]]> By: M. Bilal Fazal http://blog.laststation.net/2007/10/14/extending-seam-components/#comment-33 M. Bilal Fazal Tue, 06 May 2008 08:31:05 +0000 http://laststation.net/2007/10/14/extending-seam-components/#comment-33 Hi! Nice article. Leo: You can access new method by cast the Identity.instance() down to CustomIdentity. But i still face a problem accessing the method of CustomIdenity in pages.xml like this How can i tell seam to properly cast identity to CustomIdentiy. Can anyone help. thanks Hi!
Nice article.
Leo: You can access new method by cast the Identity.instance() down to CustomIdentity.

But i still face a problem accessing the method of CustomIdenity in pages.xml like this

How can i tell seam to properly cast identity to CustomIdentiy. Can anyone help.

thanks

]]> By: John Genoese http://blog.laststation.net/2007/10/14/extending-seam-components/#comment-34 John Genoese Mon, 24 Mar 2008 14:49:47 +0000 http://laststation.net/2007/10/14/extending-seam-components/#comment-34 Perhaps Identity.instance() is returning the original Seam class, in which newProp is not defined. Have you tried adding an instance method to your class and using "YourClass.instance()" instead? I'm a newbie myself, but if this helps, I'm glad. Perhaps Identity.instance() is returning the original Seam class, in which newProp is not defined. Have you tried adding an instance method to your class and using “YourClass.instance()” instead? I’m a newbie myself, but if this helps, I’m glad.

]]> By: Leo http://blog.laststation.net/2007/10/14/extending-seam-components/#comment-31 Leo Wed, 27 Feb 2008 04:24:28 +0000 http://laststation.net/2007/10/14/extending-seam-components/#comment-31 Hello, I am trying to do something similar to what Nuno did. I extended Identity so that I can add a new attribute that I need to use in Authenticator.authenticate. The code looks pretty much the same, except that I am extending identity. The issue am having is that the getNewProp (below) is not recognized as part of Identity, which I thought it would: String sUsername = Identity.instance().getUsername(); String sPassword = Identity.instance().getPassword(); String sNewProp = Identity.instance().getNewProp(); Do I need to make other changes for this to happen? Thanks Hello,

I am trying to do something similar to what Nuno did. I extended Identity so that I can add a new attribute that I need to use in Authenticator.authenticate. The code looks pretty much the same, except that I am extending identity. The issue am having is that the getNewProp (below) is not recognized as part of Identity, which I thought it would:

String sUsername = Identity.instance().getUsername();
String sPassword = Identity.instance().getPassword();
String sNewProp = Identity.instance().getNewProp();

Do I need to make other changes for this to happen?

Thanks

]]> By: Nuno Caneco http://blog.laststation.net/2007/10/14/extending-seam-components/#comment-32 Nuno Caneco Fri, 22 Feb 2008 16:53:12 +0000 http://laststation.net/2007/10/14/extending-seam-components/#comment-32 Thank you for this great article. I've used this mechanism on my new application and it worked just fine. In my case, I used it not to implement another login mechanism, but to add more fields to the authentication process. On my application, the user must authenticate with username, password and location id (which will be automatically filled in the future). This is my version of the extended class: @Name("org.jboss.seam.security.identity") @Scope(ScopeType.SESSION) @Install(precedence=Install.APPLICATION) @BypassInterceptors @Startup public class MyExtendedIdentity extends RuleBasedIdentity { private Integer posId; public MyExtendedIdentity() { super(); } public Integer getPosId() { return posId; } public void setPosId(Integer posId) { this.posId = posId; } } Newbies, don't forget to add the default constructor to your extended class. Another remark is that I am using Drools for the authorization process. So, I had to extend my class from org.jboss.seam.security.RuleBasedIdentity and not org.jboss.seam.security.Identity. Thank you for this great article.
I’ve used this mechanism on my new application and it worked just fine.

In my case, I used it not to implement another login mechanism, but to add more fields to the authentication process. On my application, the user must authenticate with username, password and location id (which will be automatically filled in the future).

This is my version of the extended class:

@Name(“org.jboss.seam.security.identity”)
@Scope(ScopeType.SESSION)
@Install(precedence=Install.APPLICATION)
@BypassInterceptors
@Startup
public class MyExtendedIdentity extends RuleBasedIdentity {

private Integer posId;

public MyExtendedIdentity() {
super();
}

public Integer getPosId() {
return posId;
}

public void setPosId(Integer posId) {
this.posId = posId;
}
}

Newbies, don’t forget to add the default constructor to your extended class.

Another remark is that I am using Drools for the authorization process. So, I had to extend my class from org.jboss.seam.security.RuleBasedIdentity and not org.jboss.seam.security.Identity.

]]>