[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1446:
--------------------------------
Summary: Prepare Quickstarts for Release (was: Prepare QUickstarts for Release)
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> * The tag should reference the latest release, rather than a snapshot
> * Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1446) Prepare QUickstarts for Release
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1446:
-----------------------------------
Summary: Prepare QUickstarts for Release
Key: JBTM-1446
URL: https://issues.jboss.org/browse/JBTM-1446
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
* The tag should reference the latest release, rather than a snapshot
* Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
* General check over looking for things that won't work with a tagged/released AS7+Narayana.
--
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
11 years, 10 months
[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: 24/Jan/13 11:06 AM
Start Date: 24/Jan/13 4:30 AM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day, 2 hours (was: 1 day, 7 hours)
Time Spent: 2 days, 6 hours (was: 2 days, 1 hour)
Worklog Id: (was: 12428503)
> 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: 2 days, 6 hours
> Remaining Estimate: 1 day, 2 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
11 years, 10 months
[JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1099:
--------------------------------
Issue Type: Feature Request (was: Task)
> WS-BA to 2xJTA bridge
> ---------------------
>
> Key: JBTM-1099
> URL: https://issues.jboss.org/browse/JBTM-1099
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when if a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce the TXFramework
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ]
Paul Robinson logged work on JBTM-1391:
---------------------------------------
Author: Paul Robinson
Created on: 24/Jan/13 10:39 AM
Start Date: 24/Jan/13 10:39 AM
Worklog Time Spent: 20 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 4 hours (was: 1 day, 3 hours, 40 minutes)
Time Spent: 4 hours, 40 minutes (was: 4 hours, 20 minutes)
Worklog Id: (was: 12428502)
> Prepare a blog post to introduce the TXFramework
> ------------------------------------------------
>
> Key: JBTM-1391
> URL: https://issues.jboss.org/browse/JBTM-1391
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Documentation, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 4 hours, 40 minutes
> Remaining Estimate: 4 hours
>
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into TXBridge component
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1364:
--------------------------------
Priority: Minor (was: Major)
> Migrate "REST-AT to JTA" bridge into TXBridge component
> -------------------------------------------------------
>
> Key: JBTM-1364
> URL: https://issues.jboss.org/browse/JBTM-1364
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator, REST, TxBridge
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> The task is to the work Gytis did on his internship and migrate it into the TXBridge project.
> Tasks:
> 1. Review the current solution looking for:
> 1.1 Major issues that prevent an initial release
> 1.2 Test coverage
> 2. Make any required changes
> 3. Merge into the TXBridge project
> 4. Migrate the quickstarts accross
> 5. Create a blog post
> 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy.
--
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
11 years, 10 months