January 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-909) Add an API hook for deferred afterCompletion

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-909?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson resolved JBTM-909. -------------------------------- Fix Version/s: (was: 4.16.0.Final) Resolution: Won't Fix Please re-open should the need arise > Add an API hook for deferred afterCompletion > -------------------------------------------- > > Key: JBTM-909 > URL: https://issues.jboss.org/browse/JBTM-909 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: Tom Jenkinson > Priority: Optional > > Provide an API for deferring afterCompletion callback. This comes in two parts: > # A flag to pass to the commit method indicating that afterCompletion should be deferred > # A separate method indicating that afterCompletion callbacks should proceed -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1164) social network release annoucements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1164?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1164. --------------------------------- Resolution: Duplicate Issue We already have the blog > social network release annoucements > ----------------------------------- > > Key: JBTM-1164 > URL: https://issues.jboss.org/browse/JBTM-1164 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > tweet/fb/Google+ > can be done with a cc to jboss-announce(a)redhat.com -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1164) social network release annoucements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1164?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1164: --------------------------------- > social network release annoucements > ----------------------------------- > > Key: JBTM-1164 > URL: https://issues.jboss.org/browse/JBTM-1164 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > tweet/fb/Google+ > can be done with a cc to jboss-announce(a)redhat.com -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-26) Change package structure

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-26?page=com.atlassian.jira.plugin.sy... ] Tom Jenkinson reopened JBTM-26: ------------------------------- > Change package structure > ------------------------ > > Key: JBTM-26 > URL: https://issues.jboss.org/browse/JBTM-26 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Adopt JBoss Transactions package structure (org.jboss.ts.core org.jboss.ts.jts ...) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-26) Change package structure

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-26?page=com.atlassian.jira.plugin.sy... ] Tom Jenkinson resolved JBTM-26. ------------------------------- Fix Version/s: (was: 5.0.0.M3) Resolution: Won't Fix > Change package structure > ------------------------ > > Key: JBTM-26 > URL: https://issues.jboss.org/browse/JBTM-26 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Tom Jenkinson > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Adopt JBoss Transactions package structure (org.jboss.ts.core org.jboss.ts.jts ...) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-30) Update documentation for package structure changes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-30?page=com.atlassian.jira.plugin.sy... ] Tom Jenkinson resolved JBTM-30. ------------------------------- Fix Version/s: (was: 5.0.0.M3) Resolution: Won't Fix > Update documentation for package structure changes > -------------------------------------------------- > > Key: JBTM-30 > URL: https://issues.jboss.org/browse/JBTM-30 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Documentation, JTA, JTS, XTS > Reporter: Mark Little > Assignee: Tom Jenkinson > > Once the package structure changes to org.jboss the docs need changing (as well as QA, training materials etc.) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-30) Update documentation for package structure changes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-30?page=com.atlassian.jira.plugin.sy... ] Tom Jenkinson reopened JBTM-30: ------------------------------- > Update documentation for package structure changes > -------------------------------------------------- > > Key: JBTM-30 > URL: https://issues.jboss.org/browse/JBTM-30 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Documentation, JTA, JTS, XTS > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > > Once the package structure changes to org.jboss the docs need changing (as well as QA, training materials etc.) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-989) Consider using a common code style throughout Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-989?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson resolved JBTM-989. -------------------------------- Fix Version/s: (was: 4.17.0) Resolution: Won't Fix > Consider using a common code style throughout Narayana > ------------------------------------------------------ > > Key: JBTM-989 > URL: https://issues.jboss.org/browse/JBTM-989 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Tom Jenkinson > > I think we should consider using a common code style throughout the TS project. The benefits of doing this are as follows: > # You can automate code formatting. This is a real productivity boost as you can type away, thinking about your code, rather than the style. When you hit save, or trigger it directly, the code is formatted. > ## This is not possible without a project wide code style as you too frequently re-format code that needs to stay in someone else's personal style. You can't commit this changed code as; a) it may annoy the "owner" and b) it results in a change that can't be diffed (every line may be changed). > # We get consistency over the whole project, making it easier to read code written by others. > # We have to do this anyway for code we maintain inside the JBossAS project as the project refuses to build if it doesn't adhere to their style. > Personally, I like the style I've used for the last 10 years. I find it harder to read code that is not in this style. Hence I can understand why people may object to changing their style. However, this is the very reason why a common style is beneficial. You can get used to a new style and once you do, the entire project will be styled in the way that you are used to. Providing the style is sensible, I would much rather use a style consistent across the projects I work on. I'm happy for that style to be different to my current style. > As I stated above JBossAS mandates a style at build time. I don't particularly like the style (braces should occupy their own line, IMO) but I'm happy to go with this one if it becomes the Narayana standard style. > I think we should also break the build for violations. This should prevent mistakes making their way into SVN. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-989) Consider using a common code style throughout Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-989?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson reopened JBTM-989: -------------------------------- > Consider using a common code style throughout Narayana > ------------------------------------------------------ > > Key: JBTM-989 > URL: https://issues.jboss.org/browse/JBTM-989 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.0 > > > I think we should consider using a common code style throughout the TS project. The benefits of doing this are as follows: > # You can automate code formatting. This is a real productivity boost as you can type away, thinking about your code, rather than the style. When you hit save, or trigger it directly, the code is formatted. > ## This is not possible without a project wide code style as you too frequently re-format code that needs to stay in someone else's personal style. You can't commit this changed code as; a) it may annoy the "owner" and b) it results in a change that can't be diffed (every line may be changed). > # We get consistency over the whole project, making it easier to read code written by others. > # We have to do this anyway for code we maintain inside the JBossAS project as the project refuses to build if it doesn't adhere to their style. > Personally, I like the style I've used for the last 10 years. I find it harder to read code that is not in this style. Hence I can understand why people may object to changing their style. However, this is the very reason why a common style is beneficial. You can get used to a new style and once you do, the entire project will be styled in the way that you are used to. Providing the style is sensible, I would much rather use a style consistent across the projects I work on. I'm happy for that style to be different to my current style. > As I stated above JBossAS mandates a style at build time. I don't particularly like the style (braces should occupy their own line, IMO) but I'm happy to go with this one if it becomes the Narayana standard style. > I think we should also break the build for violations. This should prevent mistakes making their way into SVN. -- 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, 2 months

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 logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 10/Jan/13 12:42 PM Start Date: 10/Jan/13 6:30 AM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 2 days, 7 hours (was: 3 days, 4 hours) Time Spent: 1 day, 1 hour (was: 4 hours) Worklog Id: (was: 12428328) > 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 > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 1 day, 1 hour > Remaining Estimate: 2 days, 7 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, 2 months

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 January 2013