Reloading services after changes to included property values
mmoayyed at unicon.net
Sun Dec 13 08:38:04 EST 2015
Yes, we have. The project you are referring to below works fine for a POC.
It's not without limitations but it works fine. It is however perfectly
unsafe for production use. It was just an idea at the time I started playing
around with refreshable Spring contexts.
To "correctly" do this, you have the following options:
1. Ditch Spring's property placeholder machinery, use your own. Most folks
that go this route tend to use Apache's configuration lib
2. Figure out how to rework the POC below to work with Spring4 and make it
3. Use @RefreshScope and Spring cloud to handle this.
#3 is the best option.
> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Tom Zeller
> Sent: Thursday, December 10, 2015 2:22 PM
> To: Shib Users <users at shibboleth.net>
> Subject: Re: Reloading services after changes to included property values
> >> When do properties files get read? Only at IDP start-up, or each time a
> service is reloaded? Is there some way to force the IDP to re-read the
> properties files so that I don't have to restart the IDP if I change a
> value in
> one of them?
> > They're static, that's why they're bad for routine uses. They're good
> > for
> structural "how it's deployed" decisions that don't change much.
> I’m curious if Unicon has had any luck with “dynamic properties” :
> To unsubscribe from this list send an email to users-
> unsubscribe at shibboleth.net
More information about the users