Evaluable criteria

[Cantor, Scott]

On 6/1/15, 9:31 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:


>
>Right, but then the *caller* has to know about the internal impl details 
>of the component(s) consuming the criteria.  And if the criteria are used 
>against multiple target types in the same component (or in chained 
>components, etc), then you have a fundamentally
> unsolveable problem.

That's basically what I was going to say...you don't know what T is in the 
generic, basically, and it isn't even necessarily just one thing. And 
whatever it might be is likely an internal implementation detail of the 
thing evaluating the criteria.

>Additionally, I have a use case in IDP-701 that could benefit as well; I 
>need to implement some creative logic to look up an EntityDescriptor when 
>I don't have a true Entity ID provided by a SAML protocol message. Being 
>able to define a custom Criterion seems like the ideal approach.

It wouldn't work, but subclassing the existing plugins to add support for 
an additional Criterion subtype should work, as does adding functionality 
to the existing base classes.

-- Scott