Configuration reloading via Tomcat 7 parallel deployment ?

[Cantor, Scott]

On 11/24/13, 10:50 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>ServiceableComponent will have the expected methods (lock(), release() and
>unload()).  If we implement this as a base class to exploit Spring and
>make
>all the requisite plugins (filters, resolvers, Š) implement Closeable we
>can
>be done in about 40 lines.

That sounds fine to me. I don't see any way to avoid the synchronization.

>For the reload, we can borrow a lot of the existing infrastructure, but I
>also propose to jettison all the code around multiple states and
>performance
>tracking.  None of this has any homologs in V2 and, I feel, represents
>³work
>in progress² towards a design which was not completed.  We have cases to
>track the needs that this addresses and we can leave the base classes
>(net.shibboleth.idp.log.EventLogger and
>net.shibboleth.idp.log.PerformanceEvent) in place.

Yeah, I think we can table that work for now. I also really thought we
needed to look at mbeans if we were going to support that kind of thing.

-- Scott