Reusing pages for different page flows?

[whafrog]

The answer is probably simple, but I'm having trouble reusing pages for different flows.

I want to define two possible modes:

1. Edit mode: select criteria --> edit stuff --> review/confirm

2. View mode: select criteria --> review

The view mode shares the first and last pages of the edit mode. How do I keep track of which mode?

I've tried using two <s:link>s on a menu each with their own <f:param> to send a request parameter. The action class picks it up and sees it, but if the user starts, say, an edit mode conversation, and halfway through starts a view mode conversation, the original mode setting is retained. What I'd really like to do (in this case) is kill the edit mode conversation, and start a fresh view mode conversation.

Any good examples of this out there?

Thanks,

Jon

[pmuir]

You are there really, just disable conversation propagation when changing between conversations.

[whafrog]

I'd appreciate a working example. Adding <f:param name="conversationPropagation" value="none"/> to my link resulted in no end of different troubles, and I gave up when getting a null pointer clicking the view mode link after initiating an edit mode sequence, where the Seam Blackbox is for some unfathomable reason trying to render components on a page I'm not even trying to navigate to.

Seam is like great drugs with terrible aftereffects. It's totally awesome, but you never know how you're going to feel the next day.