Hi Richard,
You're right, ini isn't too well suited for this use case. It was always
meant to be a simple config format, without too many 'frills'. That being
said, do you have any suggestions on how you would want this to work?
For example, Spring has the notion of a PropertiesPlaceholderConfigurer (a
mouthful) that allows you to configure one or more .properties files, and
those properties are 'merged' into one file 'view' at startup. Other beans
then reference those properties, e.g.
<property name="foo" value="${my.property.here}"/>
Depending on which environment-specific .properties file might have been
loaded, my.property.here resolves to the environment-specific value.
Is this something along the lines of what you'd like to see? If not, what
might that be? I think we're open to suggestions here - it's just without
Jira issues/feature requests, this stuff won't be improved.
Cheers,
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
On Fri, Aug 30, 2013 at 3:07 PM, [email protected]
<[email protected]>wrote:
> I think JNDI is not really suitable as a general solution to the problem.
> Although I gave the example of the database connections because I thought
> that would be the most common example familiar to people, we have several
> other parameters that need to be controlled across environments. Another
> example is a custom filter for a proxy server for some of the environments.
> A future example might be for supporting entirely different realms across
> different servers. An additional complexity is our plan to isolate the
> different environments in separate networks (AWS VPCs), which would limit
> access to network resources. So I think a more general approach to
> managing
> separate shiro.ini sections might be needed.
>
>
>
>
> --
> View this message in context:
> http://shiro-user.582556.n2.nabble.com/Best-practice-for-managing-different-shiro-ini-files-for-different-environment-tp7579099p7579102.html
> Sent from the Shiro User mailing list archive at Nabble.com.
>
