[JBoss JIRA] (JBTM-1443) Track AS 7.2.0.Alpha1
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1443:
-----------------------------------
Summary: 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
Fix For: 5.0.0.M2
--
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, 3 months
[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ]
Paul Robinson commented on JBTM-986:
------------------------------------
I'm now thinking that a WebserviceFeature is not something that is an extension point for the application or general middleware developer to use. See the following in the JAX-WS Spec:
{quote}
A JAX-WS 2.1 implementation may define its own features but they will be non-portable across all JAX-WS 2.1 implementations.
{quote}
However, We may be able to create a JBossWS specific feature, which could be OK as the client needs to run in an XTS enabled container. Getting this working in different containers would be non-trivial, but so is getting XTS working (which is a pre-requisite anyway).
> 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 day, 7 hours
> Remaining Estimate: 2 days, 1 hour
>
> 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, 3 months
[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1440?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1440:
--------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
Description:
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.
was: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?
> Move the XTS documentation into the /docs folder
> ------------------------------------------------
>
> Key: JBTM-1440
> URL: https://issues.jboss.org/browse/JBTM-1440
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> 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
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months
[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1440?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1440:
--------------------------------
Issue Type: Task (was: Feature Request)
> Move the XTS documentation into the /docs folder
> ------------------------------------------------
>
> 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
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months