Javadoc
Determines which conversation in the stack is holding the instance of this
component. A nested conversation can see context variables in all ancestor
conversations. In this case, we are interesting in knowing where that
instance was found. We are assuming that if the reference is not in an
ancestor conversation, then it must be in the current conversation. The
goal here is not to locate the instance, but rather to determine which
conversation is contributing the instance that we already know exists.
The low-level interaction with the session context should be refactored
out. The problem is that it is defined in private areas of
ServerConversationContext and cannot be reused. Actually, what we really
need is a general purpose utility for analyzing the contents of each
conversation in the stack (at least the keys).