Home/ Questions/Q 6794199
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T18:11:34+00:00

Working in JBoss AS7, using Conversation Scope to manage the user’s interactions within a

  • 0

Working in JBoss AS7, using Conversation Scope to manage the user’s interactions within a browser tab.

I note that my pages get ?cid parameters appended. This is great – until the user bookmarks the page then tries to return to it! The Conversation Filter gives a “No such conversation” message.

Is there a better way of managing conversations? Perhaps an implementation or a switch to make it use hidden fields (with appropriate care in AJAX)? Alternatively I’ll have to start trying to intercept the Conversation Exception or modify the filter!

Thanks
– Richard

Further:

I’m intercepting the BeforeRestoreView event for other purpose (login handling mainly). You’d think this would work:

/**
 * @return true if there is no valid Conversation context.
 */
private boolean conversationNotActive()
{
    Context conversationContext = m_beanManager.getContext(ConversationScoped.class);
    return !conversationContext.isActive();
}

But I can’t get the context to ask if if it’s active! Will just throw a Try-Catch in for now.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    We now take a two pronged approach.

    A quite complex conversation manager detects a bad conversation Id and takes appropriate action. It responds currently to the After Restore View event. I’d like to move it earlier but am having problems deriving the view ID at this stage. I’ve written a JSF to CDI bridge to pass the events to CDI. SeamFaces would do the same, but proved too heavyweight for us.

    For a normal GET the Conversation Manager redirects to self without the cid parameter in order to cause a new conversation to be started. For a postback it returns an HTTP 410 error. The detection of dead conversation is as above. We could use a more random conversation Id when we create conversations to try to prevent collision if an ID is reused.

    The Conversation Manager will also start a conversation depending on metadata it holds about the pages. (All pages under /forms/ require a conversation in our application). It uses redirect when it does this to ensure that the CID parameter is everywhere it needs to be. This may become unnecessary if I can solve the problem of getting the form ID before RestoreView phase.

    We use the browser history API to remove the cid from the user’s browser URL window.

    • 0