Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2620

Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name


    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 6.later
    • Component/s: Configuration
    • Labels:


      With the next Major release of Narayana:
      1. We introduce a new narayana-properties.xml
      2. The narayana-jt* jars not override the properties name in their manifest but we still support that facility in case someone else is using it
      3. We change the search path to look for <user-overridden-value>.xml, narayana-properties.xml, then jbossts-properties.xml and finally arjuna-properties.xml.

      When people use the raw jars (org.jboss.narayana.jta.jta for example) then they can then provide the same narayana-properties.xml as they would if they were using the uber jar (example org.jboss.narayana.jta.narayana-jta) without a system property. It should help in a Maven enabled debugger when executing applications running in integration environments like WildFly or Spring where debugging via an uber jar adds an extra layer that makes getting to the real source code harder and code fix cycle slower.

      This should not pose too much of a backwards compatibility issue unless the user has multiple config files with different names (arjuna and jbossts) in their path, were only using arjuna.jar and now jbossts-properties.xml was picked up. But for this reason I propose waiting until Narayana 6.

        Gliffy Diagrams




              • Assignee:
                tomjenkinson Thomas Jenkinson
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created: