Idp v311 installation at non-default loc

Brent Putman putmanb at
Fri May 22 15:20:50 EDT 2015

On 5/22/15 2:41 PM, Misagh Moayyed wrote:
> Got it, thanks. 
> It might be easier if you had template config in the configuration

I don't actually follow what you mean by "template config".  And in
what configuration (where).

> for additional property resources or if there was a way I could tell
> the initializer to “look here”.

Actually, I checked and I mis-spoke.  The idp.home isn't resolved from
PropertySources.  The initializer has a list of locations (which
defaults to the single idp.home system prop) that is used to locate the
conf/ which is loaded and used to construct a
PropertiesPropertySource.  So there's sort of a chicken/egg problem
regarding where to look.  There's levels of indirection, but at some
point you have to just say: I'm going to check this list of well-known

> (The latter may already be allowed. Don’t remember if the component
> has a setter for that sort of thing). Issue being, I’d much rather
> modify the Idp config and keep it around, than to modify Tomcat’s
> config or sys env vars etc.

You could achieve this I believe by just extending
IdPPropertiesApplicationContextInitializer and overriding
getSearchLocations(), and set this initializer impl in web.xml.  I think.

The only other way I can think of is:  if the
ConfigurableApplicationContext passed to the initializer has been
populated with the ServletContet at the time of the call, then I
suppose it could look at a servlet context param or something.  But I
don't off-hand know if this is possible.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list