Session Listener: @Startup for session scoped component

[liudan2005]

At moment, if you have @Startup in your class, your component gets initialised no matter it's session scoped or application scoped. In some occasions, you might want to do some initialization and outject the component when session is created. For example, you might need to retrive the user info for personalized home page. In this case, it would be nice to have a session scoped component that gets trigger when session is created. i.e. a session scoped component with @Startup annotation should be triggered only when a new session is created.

Had a look at seam source code and I think it should be easy to implement this by adding some code to SeamListener and Lifecycle.

[jameswoodward]

To trigger a method to run when a session scoped component is created use the @Create annotation.

@Create
public void init() {
.....
}

[liudan2005]

@Create method only gets trigger when your component is referenced in a jsf page and the page is requested by the user. If your site has many entrances, this is gonna be a problem.

[gavin.king]

"liudan2005" wrote:
At moment, if you have @Startup in your class, your component gets initialised no matter it's session scoped or application scoped. In some occasions, you might want to do some initialization and outject the component when session is created. For example, you might need to retrive the user info for personalized home page. In this case, it would be nice to have a session scoped component that gets trigger when session is created. i.e. a session scoped component with @Startup annotation should be triggered only when a new session is created.

Had a look at seam source code and I think it should be easy to implement this by adding some code to SeamListener and Lifecycle.

I would be happy to accept a patch that implemented this.

[liudan2005]

I've submitted the patch.
http://jira.jboss.com/jira/browse/JBSEAM-148

[gavin.king]

Cool, thanks.

[xtia004]

I applied @Startup to a class and @Create to a method of the class. At the method, I want to do something and set a component to session scope. I tried: @In Context sessionContext;, no matter set create and requested to true or not, sessionContext is always null. I also tried @Out(scope=ScopeType.SESSION) private Operator currentUser;, no matter set requested to true or not, it is not outjected to session. I guess at the moment, the session context is not instanced. What to do if I want to initialize something right after a session created but before any other actions taken.

[gavin.king]

Right, there is no session context (or any HttpSession) at web-app initialization time.

(Assuming that the component with the @Startup annotation is application-scoped.)

[xtia004]

Thanks, is or will be there a resolution to deal with this case?

[pmuir]

What session do you expect to be available when the web app is initialising?

[gavin.king]

No, no resolution, what you are asking for makes no sense.