SessionScoped Managed bean injection is not working

Question

This is my SessionScoped managed bean :

import javax.enterprise.context.SessionScoped;
import javax.inject.Named;

@Named("clientSessionBean")
@SessionScoped
public class ClientSessionManagedBean implements Serializable {
...
}

This is my requestscoped managed bean

import javax.enterprise.context.RequestScoped; 
import javax.inject.Inject;
import javax.inject.Named;   

@Named("myBean")
@RequestScoped
public class MyManagedBean {

 @Inject
 private ClientSessionManagedBean clientSessionBean;
 ..
 }

The value clientSessionBean giving me null .

How can I inject a sessionScoped bean in a requestscoped managed bean ?

Is there any problem with the package ?

`MyManagedBean` is a controller? or it is used from a controller? — Naman Gala, May 11 '15 at 06:30
No I used only in my jsf file , it is not used in any controller — Sujith PS, May 11 '15 at 06:31
Can you add post construct and pre-destroy method i you session scoped bean and try to check when pre-destroy method is called. — Naman Gala, May 11 '15 at 06:38
And can you check your code without implementing Serializable interface in session scoped bean. — Naman Gala, May 11 '15 at 06:41
Do you use the sessionScoped bean somewhere in your page? Check with a @PostConstruct if it is created at all — Kukeltje, May 11 '15 at 07:21
I'm assuming you've tried the most basic - is the `beans.xml` in the right place? — John Ament, May 11 '15 at 10:42
Are you trying to access the injected bean in the constructor of the target? — kolossus, May 11 '15 at 13:38
Yes.. Exactly. I was trying to access the injected bean in constructor. — Sujith PS, May 11 '15 at 13:48
Instead of injecting in the constructor use the @PostConstruct method — Kesavacharan, May 11 '15 at 20:35

score 2 · Accepted Answer · edited May 23 '17 at 11:59

Injected resources are available only after the constructor has run, i.e. during @PostConstruct and beyond. From the spec docs for JSR-250:

The PostConstruct annotation is used on a method that needs to be executed after dependency injection is done to perform any initialization

As you should be able to infer from the excerpt above, the sequence of events in the lifecycle of a bean is:

Initialization i.e. calling the constructor (the actual mechanism is more complex, but it boils down to this)
Performing injections
Call lifecycle callback, i.e. @PostConstruct. It's at this point, that you're allowed to make use of anything that was created in #2

Why use @PostConstruct?
Initialization of List in a JSF Managed bean (point #3)

SessionScoped Managed bean injection is not working

1 Answers1