>From my understanding it has always worked this way. Here is a JIRA issue
>that requests documentation of the subject and references some earlier
>postings (all the way back to 1.0.1GA):
http://jira.jboss.com/jira/browse/JBSEAM-1886
I wrote a blog posting last night that describes the convers
Did Seam always work this way? If not, what version started to behave in this
manner.
I was under the same assumption as whafrog.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112622#4112622
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
Yes, thank you!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112420#4112420
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112420
___
jboss-user mailing list
jboss-user@list
No, in this case that would be the foreground conversation which means that it
would only timeout if the session timed out. Now, if the user was to navigate
elsewhere and a different conversation was started, the previous conversation
would then become a background conversation. In that case,
Example:
User logs in and is presented with a menu page. They click a menu option,
starting a conversation that lasts for three pages. If they get up and walk
away after getting to page 2, shouldn't the new conversation time out after 2
minutes? They would still be logged in, but the convers
Sorry, should have previewed. When I say the foreground conversation never
times out, I mean that it is tied to the session timeout not the configured
conversation-timeout.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112385#4112385
Reply to the post :
h
When you say you abandon the conversation what do you mean? Do you start a new
conversation and begin interacting with it? The reason I ask is because the
foreground conversation never times out. Background conversations will timeout
according to your configured conversation-timeout. Backgro
