Configuration reloading via Tomcat 7 parallel deployment ?

Cantor, Scott cantor.2 at osu.edu
Wed Nov 20 10:45:25 EST 2013


On 11/19/13, 7:45 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>Rod and I talked about our Service interface as regards resource
>reloading today, and I wonder if spinning up a new web app instance is
>an alternative to the v2 way of replacing a Spring application context
>with a new one.

I don't think so because the containers have been historically incapable
of doing that well. I'd much rather have code we know works than depend on
containers.

It would be very dismaying if Spring can't do what I managed to do in one
C++ base class.

>From what I can tell, we do not recommend reloading relying-party.xml
>[2], and it looks like attribute-filter.xml is the most frequent
>candidate, then attribute-resolver.xml.

We didn't recommend it because it was broken for a long time. I don't
think we have any strong feelings now about it.

-- Scott




More information about the dev mailing list