What do you mean by buggy?
If you end the conversation with a menu selection, you break the back button -- or more specifically, you break it once someone hits back and selects another option. If you select an item that might begin a different top-level conversation or not run in a conversation, then the option you want is is propagation="none" to simply not propagate the current conversation.
At least that's how I do menus. If any of the Seam devs need to set me straight, please do :)
Thanks for sharing your thought. Your point is well taken and I will play with that tip. If you end the conversation using using the <s:link propagation=end, then that long running conversation form that you were in should end and redirect to the specified starting form, a search form for instance.
But then I am curious, PLEASE SHED SOME LIGHT here..., if on the tree using the s:link propagation=(end or none) will be sufficient to terminate any long running conversation process(s). I wonder if doing this will have any impact on the application performance, instead of calling the action with the annotated @End explicitly.
Please refer to this threat: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103792
Gavin mentioned that he might put together a sample app using the Richfaces tree+tab components. That should be very helpful.