The WSTF interop test scenario 7 (WS-AT interop) was working on AS5 and the early EAP5 releases running on top of JBossWS-Native. However, it has not worked on more recent releases, apparently following changes made to accommodate the move to CXF as the default stack. Later releases fall foul of the presence of SoapAction declarations in the service WSDL. n.b. these changes appear to be the cause of the failure on EAP5 even though the XTS code only runs on WS-Native. Since WSTF is our only option for performing real interop with another vendor we need to get this test to work in, as a minimum, AS6/EAP6 and, preferably EAP5. This may require negotiating a change in the WSDL to remove the SoapAction declarations or it mayjst require workign out how to get the WS stack to accept their presence and still deliver the relevant messages.
Once the WSTF test is sorted out interop testing via the WSTF advertised endpoints shoud be resumed albeit probably manually. SInce SC007 adds nothgin to our QE coverage that is not already covered by the WSTX11 tests it is not critical to run this test for QE purposes. However, once we have a working interop version again it would be prudent to include an automated run of a local WSTF SC007 client against our own local server endpoint in normal XTS test runs so that we detect any brittleness introduced by the dev process as early as possible before we need to test interop via the public WSTF endpoints.