4 Replies Latest reply on Feb 5, 2016 9:44 AM by tomjenkinson

    Proposal: Changing Narayana properties file default name with Narayana 6


      Currently the default properties file name is arjuna-properties.xml unless you use one of our narayana-jt* jars where we override this default name in the manifest to jbossts-properties.xml.

      With the next Major release of Narayana I would propose the following:

      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.


      A good win here is that when people use the raw jars (org.jboss.narayana.jta.jta for example) then they can 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.


      Any support or objection?