February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1471) Apply 'TXFramework Repositioning' to the Quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1471?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1471: -------------------------------- Summary: Apply 'TXFramework Repositioning' to the Quickstarts (was: Apply "TXFramework Repositioning" to the Quickstarts) > Apply 'TXFramework Repositioning' to the Quickstarts > ---------------------------------------------------- > > Key: JBTM-1471 > URL: https://issues.jboss.org/browse/JBTM-1471 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > * Move quickstarts into XTS, REST or TXBridge. > * Rename existing QS as raw or remove if no longer applicable. > * Upgrade the TXBridge one to use TXF and move into XTS? > * Update the docs to simplify and remove TXFramework description. > * Add entry-point readmes > * XTS -> Web services, REST-TX -> REST? -- 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-1471) Apply "TXFramework Repositioning" to the Quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1471?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1471: -------------------------------- Description: * Move quickstarts into XTS, REST or TXBridge. * Rename existing QS as raw or remove if no longer applicable. * Upgrade the TXBridge one to use TXF and move into XTS? * Update the docs to simplify and remove TXFramework description. * Add entry-point readmes * XTS -> Web services, REST-TX -> REST? was: * Move quickstarts into XTS, REST or TXBridge. * Rename existing QS as raw or remove if no longer applicable. * Upgrade the TXBridge one to use TXF and move into XTS? * Update the docs to simplify and remove TXFramework description. * Add entry-point readmes > Apply "TXFramework Repositioning" to the Quickstarts > ---------------------------------------------------- > > Key: JBTM-1471 > URL: https://issues.jboss.org/browse/JBTM-1471 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > * Move quickstarts into XTS, REST or TXBridge. > * Rename existing QS as raw or remove if no longer applicable. > * Upgrade the TXBridge one to use TXF and move into XTS? > * Update the docs to simplify and remove TXFramework description. > * Add entry-point readmes > * XTS -> Web services, REST-TX -> REST? -- 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=12428701&page=c... ] Gytis Trikleris logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 15/Feb/13 1:05 PM Start Date: 14/Feb/13 7:00 PM Worklog Time Spent: 6 hours Issue Time Tracking ------------------- Remaining Estimate: 4 hours (was: 1 day) Time Spent: 1 week, 1 day, 2 hours (was: 1 week, 4 hours) Worklog Id: (was: 12428701) > 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, 1 day, 2 hours > Remaining Estimate: 4 hours > > 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?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris commented on JBTM-986: -------------------------------------- I didn't find any reasonable way to put all the tests to one place and reconfigure application server to enable/disable client handler. Therefore, I'm going to creating two modules: one for tests with automatically enabled handler and one for test with automatically disabled handler. Hope it's going to be all right. > 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, 4 hours > Remaining Estimate: 1 day > > 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-1470) hudson build script copies over the wrong integration jar

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1470?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-1470: ------------------------------------ The conditional build of the AS was useful so I am reinstating that part of the fix. Note that the fix for the main issue (needlessly copying artifacts over to the AS modules directory) will stay. > hudson build script copies over the wrong integration jar > --------------------------------------------------------- > > Key: JBTM-1470 > URL: https://issues.jboss.org/browse/JBTM-1470 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > > The JIRA is low priority because it does not effect CI builds. > scripts/hudson/narayana.sh has a variable called BUILD_AS. If this is set to zero then the AS will not be built but after a narayana build the script will copy over the final jts jars to the AS modules folder (provided the AS directory is present) - this feature is useful for developer testing to avoid a full rebuild of the AS). There are 2 bugs: > - the name is still referring to the old jbossjts.XXX.jar name > - the jars should only be copied if BUILD_AS is set to zero > Note that other subsystem jars generated by a narayana build (such as xts) are not copied over. -- 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=12428699&page=c... ] Gytis Trikleris logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 15/Feb/13 7:02 AM Start Date: 14/Feb/13 11:00 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 1 day (was: 2 hours) Time Spent: 1 week, 4 hours (was: 1 week, 2 hours) Worklog Id: (was: 12428699) > 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, 4 hours > Remaining Estimate: 1 day > > 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-400) Compensation transactions for SOA Platform

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-400?page=com.atlassian.jira.plugin.s... ] Paul Robinson commented on JBTM-400: ------------------------------------ Done: JBTM-1472. Can you add some more detail to the description? As it stands, my understanding of this issue is that it's a duplicate of JBTM-1472. > Compensation transactions for SOA Platform > ------------------------------------------ > > Key: JBTM-400 > URL: https://issues.jboss.org/browse/JBTM-400 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Mark Little > > Needs serious discussions within the team. -- 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-400) Compensation transactions for SOA Platform

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-400?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-400: ------------------------------- Summary: Compensation transactions for SOA Platform (was: JTA for Compensations) > Compensation transactions for SOA Platform > ------------------------------------------ > > Key: JBTM-400 > URL: https://issues.jboss.org/browse/JBTM-400 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Mark Little > > Needs serious discussions within the team. -- 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-400) JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-400?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-400: ------------------------------- Description: Needs serious discussions within the team. (was: We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.) > JTA for Compensations > --------------------- > > Key: JBTM-400 > URL: https://issues.jboss.org/browse/JBTM-400 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Mark Little > > Needs serious discussions within the team. -- 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-1472) JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Reporter: Paul Robinson (was: Mark Little) > JTA for Compensations > --------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. -- 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