[jboss-svn-commits] JBL Code SVN: r19552 - in labs/jbosstm/trunk/XTS: WS-T/dev/src11/com/arjuna/webservices11/wsarjtx/client and 2 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Apr 14 12:45:02 EDT 2008
Author: adinn
Date: 2008-04-14 12:45:02 -0400 (Mon, 14 Apr 2008)
New Revision: 19552
Modified:
labs/jbosstm/trunk/XTS/WS-C/dev/src11/com/arjuna/webservices11/wscoor/client/WSCOORClient.java
labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsarjtx/client/WSARJTXClient.java
labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsat/client/WSATClient.java
labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsba/client/WSBAClient.java
Log:
corrected redundant addition of handlers to JaxWS client ports
Modified: labs/jbosstm/trunk/XTS/WS-C/dev/src11/com/arjuna/webservices11/wscoor/client/WSCOORClient.java
===================================================================
--- labs/jbosstm/trunk/XTS/WS-C/dev/src11/com/arjuna/webservices11/wscoor/client/WSCOORClient.java 2008-04-14 14:57:42 UTC (rev 19551)
+++ labs/jbosstm/trunk/XTS/WS-C/dev/src11/com/arjuna/webservices11/wscoor/client/WSCOORClient.java 2008-04-14 16:45:02 UTC (rev 19552)
@@ -110,13 +110,9 @@
RegistrationPortType port = service.getPort(endpointReference, RegistrationPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
Modified: labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsarjtx/client/WSARJTXClient.java
===================================================================
--- labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsarjtx/client/WSARJTXClient.java 2008-04-14 14:57:42 UTC (rev 19551)
+++ labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsarjtx/client/WSARJTXClient.java 2008-04-14 16:45:02 UTC (rev 19552)
@@ -81,14 +81,9 @@
TerminationCoordinatorPortType port = service.getPort(endpointReference, TerminationCoordinatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -120,15 +115,9 @@
TerminationParticipantPortType port = service.getPort(endpointReference, TerminationParticipantPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
- * TODO - not sure about this?
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
Modified: labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsat/client/WSATClient.java
===================================================================
--- labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsat/client/WSATClient.java 2008-04-14 14:57:42 UTC (rev 19551)
+++ labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsat/client/WSATClient.java 2008-04-14 16:45:02 UTC (rev 19552)
@@ -110,14 +110,10 @@
// CoordinatorPortType port = service.getPort(endpointReference, CoordinatorPortType.class, new AddressingFeature(true, true));
CoordinatorPortType port = service.getPort(endpointReference, CoordinatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
- /*
- * we need to configure an instance identifier handler for this port to pass the tx context
+ /*
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -149,14 +145,9 @@
ParticipantPortType port = service.getPort(endpointReference, ParticipantPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context
- * TODO - don't think this is correct here
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -186,13 +177,9 @@
CompletionCoordinatorPortType port = service.getPort(endpointReference, CompletionCoordinatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -222,15 +209,9 @@
CompletionInitiatorPortType port = service.getPort(endpointReference, CompletionInitiatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
- * TODO - don't think this is correct here
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
Modified: labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsba/client/WSBAClient.java
===================================================================
--- labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsba/client/WSBAClient.java 2008-04-14 14:57:42 UTC (rev 19551)
+++ labs/jbosstm/trunk/XTS/WS-T/dev/src11/com/arjuna/webservices11/wsba/client/WSBAClient.java 2008-04-14 16:45:02 UTC (rev 19552)
@@ -111,14 +111,9 @@
BusinessAgreementWithParticipantCompletionCoordinatorPortType port = service.getPort(endpointReference, BusinessAgreementWithParticipantCompletionCoordinatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -150,15 +145,9 @@
BusinessAgreementWithParticipantCompletionParticipantPortType port = service.getPort(endpointReference, BusinessAgreementWithParticipantCompletionParticipantPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
- * TODO - don't think this is correct here
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -188,14 +177,9 @@
BusinessAgreementWithCoordinatorCompletionCoordinatorPortType port = service.getPort(endpointReference, BusinessAgreementWithCoordinatorCompletionCoordinatorPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
@@ -225,15 +209,9 @@
BusinessAgreementWithCoordinatorCompletionParticipantPortType port = service.getPort(endpointReference, BusinessAgreementWithCoordinatorCompletionParticipantPortType.class);
BindingProvider bindingProvider = (BindingProvider)port;
/*
- * we need to configure an instance identifier handler for this port to pass the tx context either
- * outgoing or returning.
- * TODO - don't think this is correct here
+ * we have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
*/
List<Handler> customHandlerChain = new ArrayList<Handler>();
- customHandlerChain.add(new InstanceIdentifierHandler());
- /*
- * we also have to add the JaxWS WSAddressingClientHandler because we cannoy specify the WSAddressing feature
- */
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
// ok, JBossWS native has hacked this by pulling the address and reference parameters out of the endpoint
More information about the jboss-svn-commits
mailing list