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.
