JBossDeveloper

I don't follow.

Having several Conversations on the same page might be taking it one step to far at this time. Having named/parallell Conversations on the other hand seems very usefull to me.

@Begin(join=true, name="wiz_one"}
public String startWizardOne() { }

@Begin(join=true, name="wiz_two"}
public String startWizardTwo() { }

@End(name="wiz_two"}
public String commitWizardTwo() { }

@End(name= { "wiz_one", "wiz_two" } )
public String abortAll() { }

"gavin.king@jboss.com" wrote:
I don't follow.

@Name("documentFinder")
@Stateful
@Interceptors(SeamInterceptor.class)
public class DocumentFinderBean implements DocumentFinder {

 @DataModel
 private List<Document> documentList;

 @DataModelSelection
 private Document selectedDocument;

 private String searchCriteria;

 ......

 @Begin (join = true)
 public String searchDocuments() {

 ...... // Perform the search and update the documentList

 }

 .......
 // Setter/Getter
}

@Stateless

@Name("documentSelector")

@Interceptors(SeamInterceptor.class)

public class DocumentSelectorBean implements DocumentSelector {



 @In (create=true)

 private transient DocumentEditor documentEditor;



 @In (create=true)

 private transient DocumentFinder documentFinder;



 @Begin (nested = true)

 public String selectDocument() {

 documentEditor.setInstance(documentFinder.getSelection());

 return "document/details";

 }

 ......

 @Begin (nested = true)

 public String selectCriteria() {

documentFinder.setSearchCriteria(documentEditor.getSelectedPointer().getDescription());

 return documentFinder.searchDocuments();

 }

 ......
}

The idea of starting with a new conversation every time the user selects a new sidebar menu item (e.g. User Management, Add new Issue ...) is very important to me. What I have been doing is just joining the conversation every time the user selects a new sidebar item. This however left a lot of things in the conversation which was not needed ... resulting in a lot of resource wasting.

What I am going to do is use Gavin's suggestion of not propagating the conversation context

<h:commandLink action="main" value="User Management">
 <f:param name="conversationId" value="new"/>
</h:commandLink>

Note that disabling conversation context propagation is absolutely not the same thing as ending the conversation.

<h:commandLink action="main" value="User Management">
 <f:param name="conversationId" value="killAll"/>
</h:commandLink>

@Begin(otherConversationsState="killAll")
public String startFresh()

@Begin
public String startFresh()
{
conversation.killAllOthers();
....

Eveything is fine. The breadcrump displays:search[criteria1] > document [document1] > serach[criteria2].

"lcoetzee" wrote:
What would really be good for me is to have some thing to kill all the conversations when the link is clicked, and then starting a new conversation with an @Begin

Pretty difficult to believe. Use your debugger to see what is really going on.

Look at org.jboss.seam.core.Manager.restoreConversation(Map attributes, Map parameters)