<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 11/15/18 2:24 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:429D3EA5-37B9-44A3-91C1-1245FFA34EE2@osu.edu">
<pre wrap="">On 11/15/18, 2:13 PM, "users on behalf of Paul B. Henson" <a class="moz-txt-link-rfc2396E" href="mailto:users-bounces@shibboleth.netonbehalfofhenson@cpp.edu"><users-bounces@shibboleth.net on behalf of henson@cpp.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Does this only work with file backed providers or did I do something wrong?
</pre>
</blockquote>
</blockquote>
<br>
Technically it works with all the batch *reloading* ones, which are
file, HTTP and resource, and as of 3.4 the *dynamic* ones. This
one is unfortunately neither.<br>
<br>
<blockquote type="cite"
cite="mid:429D3EA5-37B9-44A3-91C1-1245FFA34EE2@osu.edu">
<pre wrap="">
Yes, though I don't imagine that's more than an oversight. Could be some reason I didn't consider, but it's moot for the time being.
</pre>
</blockquote>
<br>
<br>
Pretty sure is just an oversight. The Inline- one is neither
AbstractReloading- nor AbstractDynamic-. The DOMMetadataResolver
impl itself should work just fine, as the indexes stuff is
implemented in the even higher base class AbstractBatch-, for which
there is no corresponding abstract Spring parser, for purely
historical reasons I imagine. So this is just an IdP schema and
parser omission.<br>
<br>
I'll open a ticket.<br>
<blockquote type="cite"
cite="mid:429D3EA5-37B9-44A3-91C1-1245FFA34EE2@osu.edu">
</blockquote>
<br>
</body>
</html>