2 Replies Latest reply on Jun 29, 2012 5:11 PM by Scott Carlson

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

    Scott Carlson Newbie

      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.