The conversation will timeout. Redirect depends on whether you have defined a
no-conversation-view-id.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4119414#4119414
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4119414
The more I look at this, the more I'm starting to think this is a bug.
I removed my @Begin figuring I can just rely on the temporary conversation.
Its my understanding that I should have a temporary conversation across the
request and reply.
But even without the @Begin, I get the same error
anonymous wrote : Or, I could be way off...
Lets go with that.
After digging deeper, I found that before navigating to the page in question
(listcontacts.xhtml), the page I was navigating from started a new conversation
using @Begin in combination with @Create. Worse, it used @End with its
Ok, I think I understand the problem:
1. @Begin does not start a new conversation until after the method completes.
2. Thus, the object I created in the method was actually outjected to the
current conversation.
3. The conversation time out is not enforced until just prior to the redirect.
You may want to look at:
http://www.jboss.com/index.html?module=bbop=viewtopict=97618
If its the same issue, it has been fixed in CVS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003115#4003115
Reply to the post :
Thanks for the reply, Gavin.
Are you sure there are two conversations? Do you see two different
conversation ids
Yes, the converstation ids are different.
If so, are you sure that one is not a nested conversation of the other.
I have not used nested = true at the Begin annotation.
1. Are you sure there are two conversations? Do you see two different
conversation ids.
2. If so, are you sure that one is not a nested conversation of the other.
3. you'll probably have to use your debugger to solve this one, its hard for me
to tell whats going on from here
View the original
The first one.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994535#3994535
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994535
___
jboss-user mailing list
What exactly is the correct behaviour?
What I am heading at:
Is the conversation destroyed after a timeout, when the user the conversation
belongs to does something again?
Or is the conversation destroyed after a timeout, when any user does something?
View the original post :
This is the correct behavior.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994533#3994533
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994533
___
jboss-user mailing list
Thanks Gavin.
I need to unbound some entity from the current user (i.e. change a status in
the database), if his conversation times out, to be able to distribute that
entity to another user again.
Is there any actual SEAM-way to be notified when the conversation really
times out, or am I
I really, really don't think its a good idea to try and update the db from
*any* kind of timeout.
Remember, the server can always crash.
Are you trying to implement some kind of offline pessimistic lock?
View the original post :
You're right (thanks for reminding me of that)
anonymous wrote : I really, really don't think its a good idea to try and
update the db from *any* kind of timeout.
and you're right
anonymous wrote : Are you trying to implement some kind of offline pessimistic
lock?
View the original post :
Oh. So you can make it so your invididual request are in a time based manner.
So if i want to make sure my server responds in 10 seconds regardless?
at least thats what i am gathering from this part of the doco
Allows the conversation timeout to be set per-conversation, and the
conversation
The conversation timeout controls how quickly open conversations expire -- it's
the direct equivalent of session timeouts, but for conversations. It has
nothing to do with server timeouts, which are specific to the webserver. I
imagine for JBoss, it would be somewhere in the tomcat
cja987 wrote : The conversation timeout controls how quickly open
conversations expire -- it's the direct equivalent of session timeouts, but for
conversations. It has nothing to do with server timeouts, which are specific
to the webserver. I imagine for JBoss, it would be somewhere in the
Conversation timeouts occur during requests. If you aren't making any requests
to the server, they won't timeout.
Put a breakpoint in
org.jboss.seam.core.Manager.conversationTimeout(ExternalContext
externalContext) to see it happen.
View the original post :
17 matches
Mail list logo
