Configuration reloading via Tomcat 7 parallel deployment ?

[Cantor, Scott]

On 11/22/13, 12:46 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>>Did the V2 code have a destroy semantic on the components we reload?
>
>Yes - and in particular for the attribute resolver the databases/LDAP
>connections are destroyed, and there is all the required locking in place
>(using a toplevel read/write lock which I'd like to demote to the
>component
>level)

Yeah, I see it now. I never noticed all the locking internally to the
various service "doWork" methods. Those are self-contained so the locking
isn't exposed as part of the API, but it amounts to the same thing.

I really am hard pressed to believe Spring is sophisticated enough to do
this for us.

-- Scott