Attributes and Predicates

[Cantor, Scott]

On 5/6/14, 6:22 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>>we cannot detect at configuration time if someone has plugged a
>> Predicate<AttributeResolverContext> in to somewhere which expects a
>> Predicate<ProfileRequestContext> - you'll just get an ugly run time
>>class
>> cast exception. 
>
>Do we want to put in any blade guards to stop people injecting the wrong
>sort of Predicate?

No, we don't need two kinds. I think you misunderstood my point here.
Given a signature of Predicate<ProfileRequestContext>, you can have a
Function injected of type <ProfileRequestContext,String> to obtain the
requester.

With that, I can set a default Function that composes "lookup
RelyingPartyContext child" and "get RelyingPartyId".

Somebody can override that to inject a composition of "lookup
AttributeResolutionContext" and "get requester".

Or vice versa of course, but the point is the same.

-- Scott