I believe All you need is add

@End //!!!!!!!!!!!!!!!!
@Remove
@Destroy
public void destroy() {
   log.info('here');
   Contexts.removeFromAllContexts("selectedTimePeriod");
}

annotation there.

@Destroy - is bean related?
@Remove - either?

@Begin/@End annotations would mark your conversation properly.

Sorry, I am a little confused (and it's kinda too late or too early  in my location ;)
SFSB - Seam Front Side Bus?
I could suggest You to mark some action method method as @End and pass it to the s:link

<s:link action="#{bean.endSmth} />"

and to see what happens.

But, IMO propagation "end" should work.
May be it's worth to pass the some action and digg into Conversations/Contexts via debugging console :)

I assume my answer is still irrelevant enough. :)

+1 cent - possible solution to see what happens where - to invalidate session, reset conversation timeouts and so on.. Just to see what happens along the changes

Hi Priya,

I see Your pain now. I think I am not the right man to speak about SFSB related stuff :) Anyway, my vision of the problem:

1. conversation isn't ended


2. conversation scoped bean cleanup procedure isn't called. As I see - it should be called onto a) remove from AS 2) destroying context

So, I would suggest You to demark/divide each of this do you really have. I would suggest You to use

@Observer(value="org.jboss.seam.endConversation")
public void observeConversationEnd() {
log.info("CONVERSATION Ended");
          
}
@Observer(value="org.jboss.seam.beginConversation")
public void observeConversationStart() {
log.info("CONVERSATION Started");          
}

or similar Just to see what is the state of conversations.
And once more- I would suggest you to call Conversation.instance().end() by hand - to see that happens.

I believe You could invoke this stuff from your *.jsf via

<s:link action="#{conversation.end}">

So, what I would do myself (in order):

• Ensure conversation lifecycle through observers or smth. (In the worst case calling #{conversation.end} in action or via Seam Remoting.


• Only after that look on SFSB cleanup procedure invocation problems.