Advise needed: Conversations vs. navigation menu

[wenzlaff]

Hello,
I tried to achieve the following scenario:
1. Begin a conversation when showing an overview of items.
2. Use this conversation (using an extended persistence context) to hold the selected item using DataModelSelection.
3. Edit or delete the item
4. End the conversation.

I know that I could achieve this simple use case stateless as well, but this question is more general.

If the user ends the conversation implicit not explicit in Step 3, i.e. by using the navigation menu, the conversation still exists and prevents new conversations to be started.
Is there a general advise on how to handle conversations in combination with a application wide page navigation?

[pmuir]

Just make sure that a navigation doesn't propagate the conversation (remember non-Faces requests don't, or use an s:link with propagation="none").

[wenzlaff]

Thx for your reply, I will try your suggestion, although it won't be that easy since I'm using tomahawks panelNavigation.
But since the conversation doesn't explicitly end this way, won't the next conversation that starts on a different overview cause an error?

[pmuir]

well, as long as the navigation item will take an f:param you can do it that way (see the Seam ref docs).

You can have more than one conversation running at once, you just can't have more than one active conversation!

[wenzlaff]

The s:link tag with propagation="end" works, while the equivalent f:param tag at least sometimes doesn't.
I think I have to stick with the s:link...
Thanks for your hints, I must have missed that part in the docs ;)