Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15930

Support parial configuration files


    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • Management
    • None
    • Compatibility/Configuration

      I want to make a suggestion regarding the possibility to run wildfly with partial configuraiton files.

      I use Wildfly with Docker in many projects. Mostly I need to add JDBC Pools and security config.

      To build a new Docker image I have have to customize the standalone.xml file or standalone-microprofile.xml file and add this in my Dockerfile. See also my example in my blog.

      It would be fine if Wildfly provides a simmilar feature like OpenLiberty that I only provide the part I am interesting in and this part is merged during startup. So for example a JDBC config file would simple look like this:


              <subsystem xmlns="urn:jboss:domain:datasources:6.0">
                        <!-- my datasource -->
                      <datasource jta="true" jndi-name="java:/jdbc/office" pool-name="mydb" enabled="true" use-ccm="true">
                  <!-- my driver -->
                          <driver name="postgresql" module="org.postgresql">

      The datasoruce and driver is merged into the origin file.

      In this way users could easily upgrade the wildfly version. Currently it is necessary to copy the new standalone.xml file and customize it again.


      What do you think about that feature?


            ehugonne1@redhat.com Emmanuel Hugonnet
            rsoika ralph Soika (Inactive)
            0 Vote for this issue
            3 Start watching this issue