January 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1955) Review ALL documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1955?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1955. --------------------------------- Fix Version/s: (was: 5.0.0.CR3) Resolution: Incomplete Description Removed this as we split it into separate Jiras > Review ALL documentation > ------------------------ > > Key: JBTM-1955 > URL: https://issues.jboss.org/browse/JBTM-1955 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Paul Robinson > Assignee: Tom Jenkinson > > I think we need to read through all the documentation looking for: > 1. Out of date stuff. For example, references to file locations in AS versions prior to AS7. > 2. Irrelevant stuff. For example: XTS documents the theory of heuristics, despite having no support for them in the current protocols or implementation. > 3. Incorrect stuff. No examples, but there could be some errors. > 4. Missing stuff. Most likely for new features, not yet documented. > For 1. in particular, we should search across the entire documentation for other occurrences of the same issue, once found. For example, if a reference to bin/run.sh is found, then grep over all the other docs for other occurrences. > I think we should divide up the docs between multiple people so as to not over-burden a single individual with what is likely to be a tedious task. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1476) Document new XTS Features

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1476?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1476: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Document new XTS Features > ------------------------- > > Key: JBTM-1476 > URL: https://issues.jboss.org/browse/JBTM-1476 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR3 > > > Plan for new XTS features and docs: > # Implement new feature > # Release a milestone of 5.0.0 > # Publish a blog post shortly after release > # Refine the feature based on community feedback > # Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item) > Here's a list of features that need documenting, so far: > JBTM-986 Automatically setup the client side handler chain > JBTM-1447 Create WebserviceFeature for TXBridge > Bridging stuff -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1955) Review ALL documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1955?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1955: -------------------------------- Fix Version/s: 5.0.0.CR3 (was: 5.0.0.Final) > Review ALL documentation > ------------------------ > > Key: JBTM-1955 > URL: https://issues.jboss.org/browse/JBTM-1955 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.CR3 > > > I think we need to read through all the documentation looking for: > 1. Out of date stuff. For example, references to file locations in AS versions prior to AS7. > 2. Irrelevant stuff. For example: XTS documents the theory of heuristics, despite having no support for them in the current protocols or implementation. > 3. Incorrect stuff. No examples, but there could be some errors. > 4. Missing stuff. Most likely for new features, not yet documented. > For 1. in particular, we should search across the entire documentation for other occurrences of the same issue, once found. For example, if a reference to bin/run.sh is found, then grep over all the other docs for other occurrences. > I think we should divide up the docs between multiple people so as to not over-burden a single individual with what is likely to be a tedious task. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1476) Document new XTS Features

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1476?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1476: -------------------------------- Fix Version/s: 5.0.0.CR3 (was: 5.0.0.Final) > Document new XTS Features > ------------------------- > > Key: JBTM-1476 > URL: https://issues.jboss.org/browse/JBTM-1476 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR3 > > > Plan for new XTS features and docs: > # Implement new feature > # Release a milestone of 5.0.0 > # Publish a blog post shortly after release > # Refine the feature based on community feedback > # Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item) > Here's a list of features that need documenting, so far: > JBTM-986 Automatically setup the client side handler chain > JBTM-1447 Create WebserviceFeature for TXBridge > Bridging stuff -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2065) TestExternManageDestination::test_stored_message_schedule() hangs on Windows

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2065?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2065: ------------------------------------- Hi [~clebert], we haven't tried the branch with your master but yes, it is still an issue. Amos, is it possible for you to get a build together with Cleberts master and try to see if his fix has resolved the issue? If not, [~zhfeng] we should try to create a small Java example that demonstrates the issue. It should be possible by yanking some code out of our stompconnect module as would be called by the C clients. > TestExternManageDestination::test_stored_message_schedule() hangs on Windows > ---------------------------------------------------------------------------- > > Key: JBTM-2065 > URL: https://issues.jboss.org/browse/JBTM-2065 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.CR3 > > > http://172.17.131.2/job/btny-pulls-narayana-windows2008/523/consoleText > http://172.17.131.2/job/btny-pulls-narayana-windows2008/524/consoleText -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2065) TestExternManageDestination::test_stored_message_schedule() hangs on Windows

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/JBTM-2065?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on JBTM-2065: --------------------------------------- What is the current status on this? Is it still an issue? if it is.. how to replicate this? > TestExternManageDestination::test_stored_message_schedule() hangs on Windows > ---------------------------------------------------------------------------- > > Key: JBTM-2065 > URL: https://issues.jboss.org/browse/JBTM-2065 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.CR3 > > > http://172.17.131.2/job/btny-pulls-narayana-windows2008/523/consoleText > http://172.17.131.2/job/btny-pulls-narayana-windows2008/524/consoleText -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1184) Update documentation for Narayana and Wildfly changes

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1184?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1184: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/documentation/pull/25 > Update documentation for Narayana and Wildfly changes > ----------------------------------------------------- > > Key: JBTM-1184 > URL: https://issues.jboss.org/browse/JBTM-1184 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR3 > > > Specifically related to the naming of the components JBTM -> Narayana, JBossAS/AS7 -> WildFly and make sure the commands/config related to app server work on WildFly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2062) Add support for ceylon

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2062?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2062. ------------------------------------ Resolution: Done > Add support for ceylon > ----------------------- > > Key: JBTM-2062 > URL: https://issues.jboss.org/browse/JBTM-2062 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SPI > Affects Versions: 5.0.0.CR2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.CR3 > > > I need an interface to start and stop the transaction service. The start method should check to see if there is a JNDI provider present and, if so, make sure that our standard interfaces are bound to that provider (UserTransaction, JTATransactionManager and TransactionSynchronizationRegistry). Also, behind the scenes, it should register TransactionDriver with java.sql.DriverManager and bind any required datasources into the JNDI tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2077) byteman and jfree jars incorrectly reported as required at runtime in pom.xml

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2077?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2077: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/582 > byteman and jfree jars incorrectly reported as required at runtime in pom.xml > ----------------------------------------------------------------------------- > > Key: JBTM-2077 > URL: https://issues.jboss.org/browse/JBTM-2077 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > The jars mentioned above are not required at runtime so should not be present as such in the pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2077) byteman and jfree jars incorrectly reported as required at runtime in pom.xml

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2077: ----------------------------------- Summary: byteman and jfree jars incorrectly reported as required at runtime in pom.xml Key: JBTM-2077 URL: https://issues.jboss.org/browse/JBTM-2077 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson The jars mentioned above are not required at runtime so should not be present as such in the pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 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 January 2014