anonymous wrote : It will time out.
Thanks Christian and Amitev -- that does seem to be the intent. However it doesn't
match what I observe. Here's the order of play:
User visits WidgetList.xhtml -- this does a join="true" - perhaps creating a new
conversation, perhaps joining an existing one.
User clicks a link to end up in WidgetEdit.xhtml -- this also does a join="true"
and reuses the existing conversation. Here we're viewing Widget#1. OK so far.
User navigates directly back to WidgetList.xhtml via a menu link. (no end-conversation).
User clicks "Create Widget" button, ending up back in WidgetEdit.xhtml, but
since we've used join="true", we're still in the long running
conversation and reuse the old WidgetHome, which is holding onto the Widget#1. Instead of
a "new" widget, we're editing an old one.
I've tried marking the Create Widget button as propagation="none" and
propagation="end", but I still see the bad behavior (create widget edits the
already existing Widget#1). I've tried setting join="false,
nested="true" - that doesnt work (the old Home instance is still reused). I
can't find a way to avoid it.
Steve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078073#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...