Function use in the IdP

[Cantor, Scott]

On 11/12/14, 7:09 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>Have to think more - maybe there's a way to solve - like just overriding 
>and making the setParent(BaseContext) public on MessageContext.  Then 
>wherever we set the MC's on the PRC, just also set the parent explicitly.

Well, the problem sort of was that the navigation model is class-based, 
and I didn't think you could set two child contexts of the same type on 
the parent.

It is true that if getParent() worked, the way back down could be via the 
message context properties and not with getSubcontext(), but I just didn't 
think it was a good idea to call setParent() if you end up with a messy 
situation due to the class duplication.

It hasn't come up because we were careful to avoid factoring functionality 
in ways that required getting up to the root and back down from the 
message handlers.

-- Scott