February 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2619: -------------------------------- Summary: Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) (was: Create a quickstart to show using of the narayana-osgi-jta bundle) > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2620?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2620: -------------------------------- Component/s: Configuration > Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2620 > URL: https://issues.jboss.org/browse/JBTM-2620 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Fix For: 6.later > > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml as default property file name

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2620: ----------------------------------- Summary: Introduce narayana-properties.xml as default property file name Key: JBTM-2620 URL: https://issues.jboss.org/browse/JBTM-2620 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Tom Jenkinson Fix For: 6.later 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2620?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2620: -------------------------------- Summary: Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name (was: Introduce narayana-properties.xml as default property file name) > Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2620 > URL: https://issues.jboss.org/browse/JBTM-2620 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Fix For: 6.later > > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2481. ------------------------------- > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.13.Final > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.2.13.Final (was: 5.next) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.13.Final > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2481: ------------------------------------- I think the process is sufficiently automated. We may create a new task to trigger this automatic process in the future but for now I am happy with now NRP works. > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.13.Final > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2481: --------------------------------------- Are we not planning to make the release completely automatic and incorporating it into our CI? > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2481. --------------------------------- Resolution: Done > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2305) Incomplete tooling documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2305: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2016