This content has been marked as final. Show 1 reply
Another Seam user(Stu) and I are integrating Seam and Flex. We have made a lot of progress. In my testing of conversations I noticed that if I have a nested conversation inside of a long running conversation. When I call @End the conversationId is not Popped back to the parent converationId.
i.e. Manager.instance().getCurrentConversationId() returns the nested converationId, is this how it is intended to work?
This seems like correct behaviour - remember that @End just demotes the conversation to temporary - it doesn't end until the request is complete.