SessionScoped bean created twice per session.

[tdtappe]

Experienced with JBoss 6.0.0 Final:

I've got some SessionScoped beans that are created twice per session. And for one of the instances the @PostConstruct annotated method is not called. But looking at the callstack the instance is created by the container.

And maybe related: If I define a servlet listener the sessionCreated-HttpSessionEvent is also fired twice.

Is anybody experiencing the same behaviour? Is this a bug or a configuration problem?

--Heiko

[tdtappe]

The problem with the sessionCreated event being fired twice seems to occur only if in an observer of a the event fired in sessionCreated (via BeanManager.fireEvent) references a SessionScoped bean (via injection).

Is it not allowed to uses SessionScoped beans in the context of a sessionCreated event? Maybe the CDI session context isn't fully initialized at that time?

--Heiko

[spinner.joserodolfo.freitas.gawab.com]

Hey Heiko,
take a look at:

http://seamframework.org/Documentation/WhyIsTheConstructorInvokedTwiceWhenANormalScopedBeanIsCreated
and
http://techblog.joserodolfo.com/2011/04/the-proxied-nature-of-an-injected-bean-in-cdi/

by normal scope it means cdi managed scope

[spinner.joserodolfo.freitas.gawab.com]

Why is the constructor invoked twice when normal scoped bean is created

the proxied nature of an injected bean in cdi

It'd be very nice having an edit button on the forums

[tdtappe]

Ahhh... that explains a lot. Missed that one.
Thanks a lot, Jose!

But I still have two problems/questions:

1) Why is the sessionCreated event fired twice when using SessionScoped beans in the context of this event?
2) Why do I sometimes get injected beans with its fields set to null that should have been set via field injection?

--Heiko