What is the best place for external configuration files to work with clustered deploys

[scarlson]

We were using external environmental configuration files  (ie, properties for urls that differed production/test/qa).  These were loaded by spring via the older style conf/ directory that was added into the class path. 

Looking at this https://community.jboss.org/wiki/HowToPutAnExternalFileInTheClasspath I see the module as an option, but it says this isn't the "right" way for clustered deploys.

So what would be the best way to cover these persistent environmental properties?  I'm guessing JNDI is an option, but that seems like overkill for this.

[sfcoy]

Right now JNDI is the way to go. This is the way JEE is set up so that configuration can be reliably (and portably) distributed.

Injecting property values from JNDI with @Resource is trivially easy with the Spring Framework.

[scarlson]

I guess I'll have to live with it. 

I'm surprised that the cluster can't manage syncing modules between slaves as well.