[jbossts-issues] [JBoss JIRA] (JBTM-2357) jbossts-properties.xml not loaded if arjuna-properties-file not set in manifest

[Tom Jenkinson (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson resolved JBTM-2357.
---------------------------------
    Resolution: Rejected


I will reject this issue because it is possible to set the file name to look for via system property or via manifest entry. The default property file name can't be changed because it is in a library used by Narayana and potentially other products. If the system property approach doesn't work for you, please can you open a discussion on our forum and we can chat about the best way to do this for you: https://developer.jboss.org/en/jbosstm/

Thanks again for the report,
Tom

> jbossts-properties.xml not loaded if arjuna-properties-file not set in manifest
> -------------------------------------------------------------------------------
>
>                 Key: JBTM-2357
>                 URL: https://issues.jboss.org/browse/JBTM-2357
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>    Affects Versions: 5.0.3
>            Reporter: Toby Crawley
>            Assignee: Tom Jenkinson
>
> If the property isn't set, ConfigurationInfo falls back to looking for "arjuna-properties.xml" because of https://github.com/jbosstm/narayana/blob/master/common/classes/com/arjuna/common/util/ConfigurationInfo.java#L152. Is that default intentional, or should it have been set to "jbossts-properties.xml" as part of JBTM-482?
> We're running in to this with [Immutant|http://immutant.org], where the user can run their application as a set of jars or as an uberjar. When ran as a set of jars, the manifest from narayana-jta.jar has arjuna-properties-file set, and the jar provides a jbossts-properties.xml at the top level that gets loaded. But when the user creates an uberjar (a process we don't control), the uberjar includes the jbossts-properties.xml file from the jta jar, but does not include the arjuna-properties-file property in the manifest, which causes narayana to fail because the node id isn't set. We'd prefer the same behavior in either run mode, so currently provide an arjuna-properties.xml that is identical to the default from the jta jar to work around the issue.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)