| Get the conversation with the provided id.
Implementors should take care to manage conversation identity correctly.
Although it is not strictly required to return the same (==) Conversation
object every time this method is called with a particular conversation
id in a single execution thread, callers will expect to recieve an object
that allows them to manipulate the identified conversation. In other words,
the following is legal ConversationManager client code:
ConversationManager manager = ...;
ConversationId id = ...;
Conversation conv = manager.getConversation(id);
conv.lock();
try {
Conversation localReference = manager.getConversation(id);
// no need to lock since conversation 'id' is already locked
// even though possibly conv != localReference
localReference.putAttribute("foo", "bar");
Object foo = conv.getAttribute("foo");
}
finally {
conv.unlock();
}
Parameters:
id - the conversation id the conversation
throws:
NoSuchConversationException - the id provided was invalid |