[jbossts-issues] [JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Mon Jan 28 14:36:47 EST 2013
[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750866#comment-12750866 ]
Paul Robinson commented on JBTM-986:
------------------------------------
I've added a prototype WSTXFeature in this commit: https://github.com/paulrobinson/narayana/commit/575f61d1bc1623935fb4d87eeb9878a5e97d1813
To use this you need to build JBossWS from source. Here's the steps:
1. Add the Apache snapshot repo to your ~/.m2/settings.xml:
{code}
<repository>
<id>apache-snapshots</id>
<name>Apache SNAPSHOT Repository</name>
<url>http://repository.apache.org/snapshots/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
{code}
Build JBossWS CXF (change for your env)
{code}
svn co http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/ jbossws-cxf
cd jbossws-cxf
ant -Djboss720.home=/Users/paul/dev/jboss-as.ts/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT deploy-jboss720 -DskipTests=true
{code}
Build JBossWS API
{code}
svn co http://anonsvn.jboss.org/repos/jbossws/api/trunk jbossws-api
cd jbossws-api
mvn clean install -DskipTests
{code}
Update versions in JBossAS root pom.xml, based on this diff:
{code}
- <version.org.jboss.ws.api>1.0.1.Final</version.org.jboss.ws.api>
+ <version.org.jboss.ws.api>1.0.2-SNAPSHOT</version.org.jboss.ws.api>
- <version.org.jboss.ws.cxf>4.1.1.Final</version.org.jboss.ws.cxf>
+ <version.org.jboss.ws.cxf>4.2.0-SNAPSHOT</version.org.jboss.ws.cxf>
{code}
Build JBossAS and Narayana as normal.
You can run this TXFramework test to see this in action:
{code}
cd txframework
mvn test -Parq-remote -Dtest=org.jboss.narayana.txframework.functional.ws.at.simplePOJO.ATTest
{code}
> 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/src/test/java/org/jboss/test/ws/jaxws/samples/webserviceref/
> http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/src/test/resources/jaxws/samples/webserviceref/
> http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/src/test/ant-import/build-samples-jaxws.xml
> 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
More information about the jbossts-issues
mailing list