let me quote the reference guide:

beforeRedirect - by default, the conversation will not actually be destroyed until after any redirect has occured. Setting beforeRedirect true specifies that the conversation should be destroyed at the end of the current request, and that the redirect will be processed in a new temporary context

<navigation>
  <rule if-outcome="offers">
    <end-conversation before-redirect="true"/>
    <redirect view-id="/offers/index.xhtml" />
  </rule>
</navigation>

so in my case I set before-redirect to true in order to destroy conversational context before redirection is issued, so when the new request comes back due to redirection I get new conversational context.

If I am wrong, please correct me and explain the usage of before-redirect

let's say I have button that fires an action on some component annotated with @End, and I have long-running conversation. When invoking this method, ConversationInterceptor, as it encounters @end annotation will change state of the conversation from long-running to temporary, but the same conversation remains till Render Response has finished, which is after redirection.

@End
public String fireAction() {
....
}

How does adding before-redirect to this annotation change flow??

@End (beforeRedirect = true)
public String fireAction() {
....
}

In this case after invoking method, the state of conversation is changed from long-running to temporary, and redirection occurs, which uses the same conversation. In both cases I use the same conversation, which is before and after redirection. Still I don't see any differnce with before-redirect or without.

Of corse in both cases, the method doesn't throw any exception and returns non null string which fires navigation (in this case redirection)

tomorrow I will get familiar with thread that you advised

Seam in action 2009 says the same, paragraph 7.3.5, table 7.6.

before-redirect - if set to true, instructs Seam to terminate the conversation prior to issuing a redirect. The default is to propagate the conversation across the redirect and terminate it once the response is complete.

so why doesn't it work in my case, as I prefer getting fresh context, rather having the same after redirection

Found solution.

public class Manager
{
...
   public void endConversation(boolean beforeRedirect)
   {
      if ( isLongRunningConversation() )
      {
         log.debug("Ending long-running conversation");
         if ( Events.exists() ) Events.instance().raiseEvent(EVENT_CONVERSATION_END);
         setLongRunningConversation(false);
         destroyBeforeRedirect = beforeRedirect;
         endNestedConversations( getCurrentConversationId() );
         storeConversationToViewRootIfNecessary();
      }
   }

...
}

The problem was that interceptor didn't fire, because the conversation was temporary, isLongRunningConversation() returned false. Annontating method with @end din't affect conversation at all. To achive a goal I had to annotate method like follows:

@Begin
@End (beforeRedirect = true)
public String fireAction() {
....
}

After invoking method I promote conversation to long running, and immediately back to temporary, so beforeRedirect instructs seam to destroy conversation. In result after redirection I get fresh context, which I needed

Wang Liyu wrote on Jun 10, 2009 14:46:


Hi,
I guess you have the same issue, check this: http://www.seamframework.org/Community/HowToEndAndBeginANewConversationWithOneSignleSlink

Thanks a lot, I am facing that problem either and was looking for solution