-
1. Re: s:link with propagation="join" on expired conversation
ericjava.eric.chiralsoftware.net Nov 6, 2008 8:15 PM (in response to javacoryd)It makes sense and it's not a bug.
join is a sub-set of begin,
-------------
-
2. Re: s:link with propagation="join" on expired conversation
javacoryd Nov 6, 2008 8:32 PM (in response to javacoryd)Yes, I guess that does make sense.
Is there any way in which you can make an s:link behave, such that, if the conversation ( identified by the conversation id parameter ) is now gone that it doesn't start a new one?
Thanks,
Cory.
-
3. Re: s:link with propagation="join" on expired conversation
ericjava.eric.chiralsoftware.net Nov 6, 2008 9:27 PM (in response to javacoryd)Yes, it's possible. There may be other ways, but the way that comes to mind for me is to use a value binding, like this:
<s:link propagation="#{org.jboss.seam.core.conversation.longRunning ? 'join' : 'none'}" .... />
I haven't tested it but I assume that would do what you want.
But be certain that this is what you really want to happen before you do it.
-
4. Re: s:link with propagation="join" on expired conversation
javacoryd Nov 10, 2008 4:48 PM (in response to javacoryd)The problem I'm trying to solve is where we have an expired conversation that no longer exists. At the time the page is generated, the conversation does exist, but ( a while later ) when a link or form button is pressed, the conversation no longer exists.
If the form button is pressed, we get the expected
your conversation has expired
message, which is great. If a <s:link> is pressed, Seam starts a new conversation, which is bad.Thanks,
Cory.