Is it possible to make Shibboleth re-process the conf/attribute-filter.xml without restarting the servlet container?

[Waldbieser, Carl]

For Shibboleth IDP 2.x, is it possible to convince the software to re-read the `conf/attribute-filter.xml` settings without having to bounce the servlet container in which the software is running?  Currently, when a new AttributeFilterPolicy is added to support a new SP, our procedure has been to restart the service.  This causes an interruption of service for a brief time.  I was wondering if there is a way that the service interruption could be avoided.

Thanks,
Carl Waldbieser
ITS System Programmer
Lafayette College