[jboss-svn-commits] JBL Code SVN: r19702 - labs/jbosstm/workspace/interop/WSTX11-interop.

[jboss-svn-commits at lists.jboss.org]

Author: adinn
Date: 2008-04-23 13:01:48 -0400 (Wed, 23 Apr 2008)
New Revision: 19702

Added:
   labs/jbosstm/workspace/interop/WSTX11-interop/README.txt
Log:
detail sof JaxWS based 1.1 tests

Added: labs/jbosstm/workspace/interop/WSTX11-interop/README.txt
===================================================================
--- labs/jbosstm/workspace/interop/WSTX11-interop/README.txt	                        (rev 0)
+++ labs/jbosstm/workspace/interop/WSTX11-interop/README.txt	2008-04-23 17:01:48 UTC (rev 19702)
@@ -0,0 +1,41 @@
+This latest version of the WSTX11 test code uses the JaxWS based
+implementation of XTS 1.1 which runs on JBoss AS 5.0.0Beta4 overlaid
+with JBossWS 3.0.1 Native 2.0.4.GA.
+
+Implementation of this version of the interop code required modifying
+the interop Initiator and Participant services os that they
+communicate via JaxWS. This is because they have to use the WSCOOR
+CoordinationContext types generated by the JaxWS wsdl compiler when
+talking to the 1.1. services and hence when talking to each other
+which invaldiates use of the serialisation code in Kev's roll-yer-own
+soap stack (a plus point is that they can use use JaxB to
+serialise/deserialise these types so the switch is not very complex).
+
+One outstanding problem with using JaxWS is that the WSDL does nto
+allow any way of notifying faults associated with the asynchronous
+(oneway) protocol messages in the WS-AT and WS-BA protocols. So, in
+certain circumstances where the old code could notify a caller of an
+invalid request or a failure to process a request the JaxWS based code
+merley lgos a server-side error. This causes certain badly behaved
+programs to hang or, worse, continualy retry message sends. This
+behaviour means that two of the tests (AT5_5 and BA1_7, both of which
+exercise error conditions) fail and, in doing so, wedge the test
+program. These tests have been knobbled so they fail up front.
+
+When the test suite is run using an initiator and participant service
+located in the same JBoss server all the other tests finish
+successfuly and generate a sequence of messages satisfying all the
+requirements in the interop 1.1 AT and BA specs. The tests stil need
+to be run against competitor implementations.
+
+n.b. the Test Runner jsp interface is mapped at
+
+    http://localhost:8080/interop11/
+
+The AT test participant is mapped at
+
+    http://localhost:8080/interop11/ATParticipantService
+
+The BA test participant is mapped at
+
+    http://localhost:8080/interop11/BAParticipantService