Help with MetadataProvider -> MetadataResolver ?

[Tom Zeller]

>> Back in August you asked [1] :
>>> Did/do we have any intention of supporting queries using the
>>> MetadataResolver API that *don't* include an EntityIdCriterion?
>> and the answer, then, is yes, support queries that do not include an
>> EntityIdCriterion, correct ?
>
> Sorry I'm not following what you're asking exactly, or the context of
> the question.  I think we decided mostly, no, we didn't necessarily need
> to support queries without an EntityIdCriterion, and currently we don't,
> you'll get an exception in that case.  It would primarily be useful for
> cases like discovery or something, not the main 99.9% case of looking up
> metadata at runtime in a SAML profile flow.

I was thinking, quite unclearly, if an entity ID was required, it
would be a string parameter to a method or constructor like it was
with the MetadataProvider and not part of any criteria, but no. I
still get confused which is singular or plural, criteria or criterion,
fyi :-)

The context of this thread is updating some code (AMAAIS which I can
talk about tomorrow) which uses our "parent" pom before we split it
into parent-v2 and parent-v3. The other change is HttpClient ...

> However, when I finish up with the HttpClient hell that I've been in for
> the last couple of weeks, I'll get back to the resolver predicate stuff
> that I've mentioned.

I'll just mention in passing how much time it takes me to understand
changes to an API when I am only vaguely familiar with it. Thanks for
your notes on HttpClient.