0 Replies Latest reply on Jun 17, 2014 10:47 AM by freiser

    Using JNDI as configuration store




      I want to use Wildfly's JNDI as storage for my configuration data.

      I've thought to store the entries under java:/app/env/... as it would allow me to deploy the ear multiple times and give each of the deployments its own set of configuration entries.


      I've searched for methods how to configure this entries in the server. However I have only found the instruction "Do it by using deployment descriptors".

      This solution is not feasible for me, as it would require to repackage the application each time it gets deployed (e.g. from TEST to PRODUCTION)


      This change is not allowed and therefore I have to find a solution which would allow me to configure it in the servers configuration file (or somewhere else external).


      Can you help me in this task?


      How do you solve this task?