Fwd: Spring test client hardcoded to use the Tuscany runtime

[Jim Marino <jim.marino@gmail.com>]

Hi,

The below issue is actually worse than I initially thought. 

The class SpringTestRunner overrides the BaseJAXWSTestRunner.invoke(String) method, which is responsible for making a Web Services invocation to a service responsible for relaying the request to the composite under test. Instead, the overridden method performs a local invocation via a proprietary API that drags Tuscany dependencies into the entire test suite. In addition, there appears to be no Web Services binding configuration for any of the modules to test with.

I can work around these issues and remove the dependencies easily enough but inorder to fix this, the test cases need to have proper test services exposed as Web Services endpoints and have the client invoke them accordingly.

Jim

---------- Forwarded message ----------
From: Jim Marino <jim.marino@gmail.com>
Date: Thu, Mar 7, 2013 at 12:19 PM
Subject: Spring test client hardcoded to use the Tuscany runtime
To: sca-j@lists.oasis-open.org


Hi,

It appears the Spring test client is hardcoded to use the Tuscany runtime:

public class SpringTestRunner extends BaseJAXWSTestRunner {

protected static final URI DOMAIN = URI.create("default");

@Override

    public String invokeTest( String input ) throws Exception {

// TestService service = SCAClientFactory.newInstance(DOMAIN).getService(TestService.class, testConfiguration.getServiceName());

TestService service = TuscanyRuntimeBridge.instance.node.getService(TestService.class, testConfiguration.getServiceName());

return service.testIt(input);

    }

}

This should be changed to correspond to how other the other test suites (e.g. Assembly, Policy, WS) are implemented.

Jim