We're using seam 1.0.1 on jboss 4.0.4
I've tried having both
@Scope(ScopeType.SESSION)
and
@Conversational(ifNotBegunOutcome="front")
on my seam class. Neither are removed when I log out.
And to answer your question:
When LifeCycle.endSession(..) is called from the LoginPortlet Manager.instance
Another unexpected, atleast for me, discovery is that LifeCycle.endSession(..)
is called twice during the logout request. Is this correct?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014926#4014926
Reply to the post :
http://www.jboss.com/index.html?modul
Thanks for the help Gavin!
In LifeCycle.endSession(..):
Set conversationIds = Manager.instance().getSessionConversationIds();
is returning an empty Set so
Contexts.destroy(new ServerConversationContext(..))
is never called for any conversationId.
View the original post :
http://www.jboss.com
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014117
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014118#4014118
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014118
__
I posted the other thread. The two threads identify the same problem.
Yes SeamListener is being called.
My application's conversation and context is being removed (from
LifeCycle.java) but still my Seam EJB3s (and underlying EJB3s) are not removed!
(They are removed some time later, up until 30
I'm having problems with my JBoss Portal Seam application.
I have two portlets, one for my application and the other to handle user
actions (eg my preferences and log out).
When the user logs out in one portlet my seam actions (and it's ejb3s) are
not passivated. When the session timeouts sometime
