title: When to put configuration in file.properties or Jndi
body: <p>For a long time in many IT services, I see some complex process to manage Java EE application configuration depending of the environments: 
   - custom tools, with Database or not, to manage replacement in the properties file (unzip war, replace, zip war...)
   - Externalize properties file in obscure directory in the server (and some process to update it some time) and some time with a JNDI configuration...
   - maven profile and lot of big properties files</p>
  
  <p>But for database connection everybody use jndi datasource. </p>
  
  <p>Why this is not generalized for all configurations that depend of environment ?</p>
  
  <p><em>Update : I want deal with other variable than datasource, there is no question about datasource : it's in configured in JNDI for Java EE application. After if you want hack JNDI...</em></p>