Errors after Relying Party Service Reload

[Slaughter, Brett]

> > We are well aware of the warning on the wiki regarding use of the
> > configuration reloading in production, and we have sufficient
> > configuration testing in place to prevent invalid configurations from
> > being loaded into the production environment. The goal of using the
> > reloading features is to provide shorter turn-around when adding new
> > SPs to the IdP and modifying attributes and release policies without
> > resetting session state for all authenticated users by restarting Tomcat
> entirely.
> 
> None of those things requires reloading relying-party.xml.

The statement covered our overall intentions for use of reloading. We're
only experiencing trouble at this point with reloading of relying-party.xml
specifically.

When adding a new SP to the IdP (1:1 trust), I have to add a new
MetadataProvider element in relying-party.xml to load the SPs metadata file.
How can I add a new SP without reloading relying-party.xml?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5992 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/users/attachments/20120402/9ab204c1/attachment-0001.bin