As far as I understand nested conversations will not have their own persistence context (assuming that a parent already did some db actions).
However is there a (easy - standard) way to let a standard conversation act like a nested conversations when the conversation is ended? What I would like is that a when a conversation is ended it should resume another (i.e. the parent) conversation.
I saw that there is parentConversationIdParameter in the Manager class. Is this maybe intended for this behavior or is there another way of implementing this behavior?
Thanks for the great work with Seam!
The topic of nested conversations has been discussed in a number of (informative) posts, here is one of them: