Injection of SESSION POJO into event/session scoped POJO not

[joeyxxx]

I'm running 1.2.1 with facelets on JBoss 4.05 EJB3 profile and using pojos not EJBs. This is my first attempt at seam and the ff issue has thrown me for a bit of a loop.
The user component injected into balance is always null and it seams that I can only reference it is explictly using the ff

(User) Contexts.getSessionContext().get("user");

I wonder if my approach is totally off. Maybe I should be using some kind of factory object that Outjects the balance object.
This is the Class I'm Trying to Inject.

@Name("user")
@Scope(SESSION)
public class User implements Serializable
{
 private String userName;
 private String password;
 private String userRole;
 private String segment;
 private String firstName;
 private String lastName;
 private String destination;

 public User(String firstName, String lastName, String userName, String password)
 {
 this.firstName = "James";
 this.lastName = "Bond";
 this.password = password;
 this.setUserName(userName);
 this.setUserRole("Investor");
 }

 public User() {}

This Is the Class I'm trying to Inject Into.

@Name("balance")
@Scope(EVENT)
public class Balance implements Serializable
{
 private double totalMarketValue;
 private double cash;
 private double margin;
 private String userName;
 @In
 private User user;
 @Logger Log log;

 public Balance() {
 this.setTotalMarketValue(0);
 this.setMargin(0);
 this.setCash(0);
 if(user!=null){
 this.setUserName("Balance User:"+this.user.getUserName());
 } else {
//This always works!!!
 user = (User) Contexts.getSessionContext().get("user");
 this.setUserName("Null @In "+this.user.getUserName());
 }
 }

Are there any disadvantages to using javabeans instead of EJBs if one doesn't care about transactions etc? Is clustering better with EJBs on JBoss?
Thanks

[cwash]

Maybe a dumb question, but first one that pops in my head is... do you have getters/setters for the User on your component?

[joeyxxx]

Thanks for your reply.
I do have the getters & setters.

[joeyxxx]

I got it to work now.
Looks like the problem had to do with referencing the injected user object in the balance objects constructor. if the reference is done in a method other than the constructor, it works.

[fernando_jmt]

I will suggest you the following:

(The reasons I do this are in the Seam reference documentation)

@Name("balance")
@Scope(EVENT)
public class Balance implements Serializable
{
 private double totalMarketValue;
 private double cash;
 private double margin;
 private String userName;
 @In //it suppose the user already is in the session context (an instance)
 private User user;
 @Logger Log log;

 @Create
 public void initialize(){
 this.setTotalMarketValue(0);
 this.setMargin(0);
 this.setCash(0);
 this.setUserName(user.getUsername());
 }

}

[cwash]

I got it to work now.
Looks like the problem had to do with referencing the injected user object in the balance objects constructor. if the reference is done in a method other than the constructor, it works.

Ah, cool... yeah I'm pretty sure everything works off of setter injection. So the way the container injects your dependencies is by first creating a new instance through the default no-arg constructor and then injecting dependencies using setters for each @In annotation. That's probably why you were seeing problems.

[joeyxxx]

I do recall seeing initialize in a bunch of examples. I guess I better give the docs a once over and include an initialize skeleton in my templates.
Thanks again.

[fernando_jmt]

The name initialize does not matter. You can mane as you want, the most important thing here is the @Create annotation, which tells Seam to execute such method just after the component is successfuly initialized (all Seam components are available, ready to be injected).