February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder and check they are current

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1440?focusedWorklogId=12428713&page=... ] Paul Robinson logged work on JBTM-1440: --------------------------------------- Author: Paul Robinson Created on: 20/Feb/13 11:08 AM Start Date: 20/Feb/13 11:08 AM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 3 hours (was: 7 hours) Time Spent: 5 hours (was: 1 hour) Worklog Id: (was: 12428713) > Move the XTS documentation into the /docs folder and check they are current > --------------------------------------------------------------------------- > > Key: JBTM-1440 > URL: https://issues.jboss.org/browse/JBTM-1440 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 5 hours > Remaining Estimate: 3 hours > > It appears that there is no need to split the documentation between community/product, see JBTM-835 for details. It may be worth double checking it is all still product related, if not, leave some in XTS/docs and move the relevant parts into /docs/XTS? > We should also use this as an opportunity to check that the docs are current. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder and check they are current

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1440?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1440: -------------------------------- Summary: Move the XTS documentation into the /docs folder and check they are current (was: Move the XTS documentation into the /docs folder) > Move the XTS documentation into the /docs folder and check they are current > --------------------------------------------------------------------------- > > Key: JBTM-1440 > URL: https://issues.jboss.org/browse/JBTM-1440 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 hour > Remaining Estimate: 7 hours > > It appears that there is no need to split the documentation between community/product, see JBTM-835 for details. It may be worth double checking it is all still product related, if not, leave some in XTS/docs and move the relevant parts into /docs/XTS? > We should also use this as an opportunity to check that the docs are current. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1443) Track AS 7.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1443?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1443. --------------------------------- Resolution: Rejected Not required > Track AS 7.2.0.Alpha1 > --------------------- > > Key: JBTM-1443 > URL: https://issues.jboss.org/browse/JBTM-1443 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.0.M2 > > > https://issues.jboss.org/browse/AS7/fixforversion/12318469#selectedTab=co... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1143) Narayana with Maven Central

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1143?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1143. --------------------------------- Resolution: Done > Narayana with Maven Central > --------------------------- > > Key: JBTM-1143 > URL: https://issues.jboss.org/browse/JBTM-1143 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Try syncing from M1 onwards, so that it will be synced immediately after M2 is released. > We should also take a look at what things we depend on that are not in maven central. I said that I would take steps to reduce the number of these. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1143) Narayana with Maven Central

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1143?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1143: ------------------------------------- Joel has done his initial checks and it looks like Narayana 5.0.0.M2 will be synced with central. He will need to confirm nothing messy has slipped in once M2 is released. > Narayana with Maven Central > --------------------------- > > Key: JBTM-1143 > URL: https://issues.jboss.org/browse/JBTM-1143 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Try syncing from M1 onwards, so that it will be synced immediately after M2 is released. > We should also take a look at what things we depend on that are not in maven central. I said that I would take steps to reduce the number of these. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Work on JBTM-986 stopped by Gytis Trikleris. > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 1 week, 3 days, 1 hour > Remaining Estimate: 2 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?focusedWorklogId=12428712&page=c... ] Gytis Trikleris logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 20/Feb/13 9:07 AM Start Date: 19/Feb/13 9:06 AM Worklog Time Spent: 6 hours Issue Time Tracking ------------------- Remaining Estimate: 2 days (was: 3 hours) Time Spent: 1 week, 3 days, 1 hour (was: 1 week, 2 days, 3 hours) Worklog Id: (was: 12428712) > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 1 week, 3 days, 1 hour > Remaining Estimate: 2 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1480) On using hornetq object store native libraries are loaded automatically - it should be configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1480?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1480: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug 913117|https://bugzilla.redhat.com/show_bug.cgi?id=913117] The messaging subsystem defines element journal-type that defines the type of library which will be used. Possible values are ASYNCIO and NIO. <subsystem xmlns="urn:jboss:domain:messaging:1.2"> <hornetq-server> <journal-type>ASYNCIO</journal-type> ... For transaction subystem would be probably necessary to enhance schema. The transactions use element use-hornetq-store where would be fine to have possibility to define (as subelement or parameter) the type of libraries that will be used. > On using hornetq object store native libraries are loaded automatically - it should be configurable > --------------------------------------------------------------------------------------------------- > > Key: JBTM-1480 > URL: https://issues.jboss.org/browse/JBTM-1480 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Configuration > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > > Currently when HornetQ implementation of object store is used and native libraries (AIO) are available the native are used without user's explicit request. > It was decided that user should have possibility to define whether the native libraries will be used or not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1480) On using hornetq object store native libraries are loaded automatically - it should be configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1480?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1480: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=913117 > On using hornetq object store native libraries are loaded automatically - it should be configurable > --------------------------------------------------------------------------------------------------- > > Key: JBTM-1480 > URL: https://issues.jboss.org/browse/JBTM-1480 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Configuration > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > > Currently when HornetQ implementation of object store is used and native libraries (AIO) are available the native are used without user's explicit request. > It was decided that user should have possibility to define whether the native libraries will be used or not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1480) On using hornetq object store native libraries are loaded automatically - it should be configurable

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created JBTM-1480: -------------------------------------- Summary: On using hornetq object store native libraries are loaded automatically - it should be configurable Key: JBTM-1480 URL: https://issues.jboss.org/browse/JBTM-1480 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.17.3 Reporter: Ondřej Chaloupka Assignee: Tom Jenkinson Currently when HornetQ implementation of object store is used and native libraries (AIO) are available the native are used without user's explicit request. It was decided that user should have possibility to define whether the native libraries will be used or not. -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013