What I forgot to mention is how conversations are started in the first place. I
have an "Actions" dropdown box in the view, which triggers an
actionMenuSelectionChanged handler:
|
|
|
The actionMenuSelectionChanged method looks like this:
public void actionMenuSelectionChange
Forget the previous post, didn't work either.
However, I found out that the cases in which the ce.lock() call fails is when
the thread trying the ce.lock() is not the ConversationEntry's lock owner. I
guess that's exactly the point of this whole locking story, but I don't
understand why there a
Thanks for answering, Pete.
What I don't understand is why the first conversation in my steps-to-reproduce
scenario is locked at that point in time (when trying to switch from the active
conversation 2 back to conversation 1).
This would imply that my code for starting a new conversation
Conv
"objectbay" wrote : What does the call to ce.lock() really mean? And can
anybody explain why this would fail?
It means, get a lock on the conversation. It would fail if the conversation was
in use by another thread.
anonymous wrote : Is there a problem with calling switcher.select() from an
a
I don't think its got anything to do with how you start the conversation. You
probably just have concurrent calls to the conversation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121006#4121006
Reply to the post :
http://www.jboss.com/index.html?module=bb
Hello again,
I have put a call to ConversationEntry.unlock() into my AJAX handler, and now
conversation switching seems to work reliably:
public void actionMenuSelectionChanged() {
| ConversationEntry ce =
Manager.instance().getCurrentConversationEntry();
| if (ce != null && ce.isL
You can file a JIRA bug report for this - Ajax switching of conversations.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125920#4125920
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125920
