Attribute Lookup in Extension

[Cantor, Scott]

On 9/17/18, 1:59 PM, "Christopher Bongaarts" <cab at umn.edu> wrote:

> One thing I found helpful in understanding this was to examine the 
> existing (system) flows that call a ResolveAttributes action, and 
> compare how different flows invoke it in different ways at different times.

Certainly one can, but the "major" flows are very complex and hard to follow at first, and in this specific instance, I'm just saying that the interceptors run at a point where all the data has been collected already in the normal way and the usual need is just to access it via the AttributeContext, per the diagram of the tree on the page I referenced.

That's how they existing ones (expiring-password, context-check, and even attribute-release) get at them.

What you *don’t* want to do is ever wire up copies of our action beans and/or directly copy our flows when the beans reference those impl classes. They're not API and they're all subject to change at any time, and any upgrade could break them.

-- Scott