August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1965) Add support for XADisk

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1965?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1965: -------------------------------- Fix Version/s: (was: 6.later) > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > > We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1860: -------------------------------- Fix Version/s: 5.later > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.later > > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1860) Please document AtomicAction and TransactionStatusManager scanner.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1860: ------------------------------------- http://narayana.io/docs/project/index.html#d0e2551 (failure recovery guide online) > Please document AtomicAction and TransactionStatusManager scanner. > ------------------------------------------------------------------ > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.later > > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1860: -------------------------------- Summary: Please document TransactionStatusManager scanner. (was: Please document AtomicAction and TransactionStatusManager scanner.) > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.later > > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1856?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1856: -------------------------------- Issue Type: Task (was: Feature Request) > Provide a transactional driver quickstart > ----------------------------------------- > > Key: JBTM-1856 > URL: https://issues.jboss.org/browse/JBTM-1856 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Provide a simple example of a standalone application using Narayana with Transactional Driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1856?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1856: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Provide a transactional driver quickstart > ----------------------------------------- > > Key: JBTM-1856 > URL: https://issues.jboss.org/browse/JBTM-1856 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Provide a simple example of a standalone application using Narayana with Transactional Driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1820: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang(a)redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1820: -------------------------------- Priority: Optional (was: Major) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang(a)redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1820: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang(a)redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2489) Create a separate CI job for running findbugs

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2489?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2489. ------------------------------------ Resolution: Done I have added html findbugs generation to the narayana-codeCoverage job and disabled it in the MAIN profile > Create a separate CI job for running findbugs > --------------------------------------------- > > Key: JBTM-2489 > URL: https://issues.jboss.org/browse/JBTM-2489 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.later > > > Set up a job for running the findbugs profile and remove it from the default profile. Also add the site goal so that we can archive the html report. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 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 August 2015