title: Axis2 webservice (aar archive) properties file
body: <p>I'm currently developing a set of SOAP webservices over <em>Axis2</em>, deployed over a clustered <em>WebLogic</em> 10.3.2 environment.</p>
  
  <p>My webservices use some user settings that I want to be editable without the need for recompiling and regenerating the AAR archive. With this in mind, I chose to put them into a <code>properties</code> file that is loaded and consumed in runtime.</p>
  
  <p>Unfortunately, I'm having some questions about this:</p>
  
  <p>As far as I know, to achieve what I want, the only option is to put the properties file into the <code>../axis2/WEB-INF/classes</code> directory of each one of the deployments (on each <em>WebLogic</em> instance) I currently have on my clustered configuration, and then load the file, as follows (or equivalent, this has not been verified for optimization):</p>
  
  <pre><code>InputStreamReader fMainProp = new InputStreamReader(this.getClass().getResourceAsStream("myfile.properties"));
  Properties mainProp = new Properties();
  mainProp.load(fMainProp);
  </code></pre>
  
  <p>This is not as practical as I wanted it to be, because each time I want to alter some setting on the properties file, I have to edit each one of the files (deployed over different <em>WebLogic</em> instances) and there is a high probability of modifying one of these files without modifying the others.</p>
  
  <p>What I would like to know is if there is any (better) alternative to accomplish what I want, minimizing the potential conflict of configuration that is created by distributing and replicating the properties file through multiple <em>WebLogic</em> instances.</p>