WSDL – My Shitty Code

Spring Web Services: Client Integration Testing with MockWebServiceServer

Shitty Author — Thu, 03 Apr 2014 02:23:42 +0000

Spring Web Services provides a great way to perform web service client integration tests. However, the example in the documentation requires the client class to extend org.springframework.ws.client.core.support.WebServiceGatewaySupport, which is rather ugly. Instead, I prefer to have WebServiceTemplate injected into my client class.

So, I made a slight tweak to my integration test to work this work…

Production Code To Be Tested

First, we need the following Spring Web Services dependency:


    org.springframework.ws
    spring-ws-core
    2.1.4.RELEASE

Let’s assume the client class looks like this:-

@Service
public class WSClientServiceImpl implements WSClientService {

    private WebServiceTemplate webServiceTemplate;

    @Autowired
    public WSClientServiceImpl(WebServiceTemplate webServiceTemplate) {
        this.webServiceTemplate = webServiceTemplate;
    }

    public String login(String username, String password) {
        Login login = new ObjectFactory().createLogin();
        login.setUsername(username);
        login.setPassword(password);

        SoapActionCallback callback = new SoapActionCallback("http://webservice/login");
        Object object = webServiceTemplate.marshalSendAndReceive(login, callback);

        JAXBElement jaxbElement = (JAXBElement) object;
        String sessionId = jaxbElement.getValue();

        return sessionId;
    }
}

The WebServiceTemplate bean is configured like this:-

...

Constructing Integration Test

Make sure we have the Spring Web Services Test framework dependency:-


    org.springframework.ws
    spring-ws-test
    2.1.4.RELEASE
    test

The integration test looks similar to the example in the Spring documentation, however, I injected WebServiceTemplate instead:-

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration({"classpath*:applicationContext.xml"})
public class WSClientServiceImplTest {

    @Autowired
    private WSClientService wsClientService;

    @Autowired
    private WebServiceTemplate webServiceTemplate;

    private MockWebServiceServer mockServer;

    @Before
    public void createServer() throws Exception {
        mockServer = MockWebServiceServer.createServer(webServiceTemplate);
    }

    @Test
    public void testLogin() {
        Source requestPayload = new StringSource(
                "" +
                "  user" +
                "  password" +
                ""
        );

        Source responsePayload = new StringSource(
                "12345"
        );

        mockServer.expect(payload(requestPayload)).andRespond(withPayload(responsePayload));

        String sessionId = wsClientService.login("user", "password");

        assertThat(sessionId, is("12345"));

        mockServer.verify();
    }
}

The post Spring Web Services: Client Integration Testing with MockWebServiceServer appeared first on My Shitty Code.

The message with Action ” cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher

Shitty Author — Tue, 01 Oct 2013 20:29:25 +0000

PROBLEM

You get this error message when invoking a web service:-

org.springframework.ws.soap.client.SoapFaultClientException: The message with Action ” cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

SOLUTION

You forgot to specify the SOAP action before invoking the web service.

Open your WSDL file and search for the operation you are trying to invoke. You should see something like this:-

Take note of the soapAction value, in this example, it is http://oh.my.gawd.

If you are using Spring Web Services, add the following lines:-

@Autowired
private WebServiceTemplate webServiceTemplate;

public void run() {
	ObjectFactory objectFactory = new ObjectFactory();

	// Create the request payload
	OhMyGawd ohMyGawd = objectFactory.createOhMyGawd();
	ohMyGawd.setValue(...);

    OhMyGawdResponse response = (OhMyGawdResponse) webServiceTemplate.marshalSendAndReceive(
            ohMyGawd,
			new SoapActionCallback("http://oh.my.gawd")
	);

	...
}

The post The message with Action ” cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher appeared first on My Shitty Code.

Cannot process the message because the content type ‘application/soap+xml; charset=utf-8’ was not the expected type ‘text/xml; charset=utf-8’

Shitty Author — Tue, 01 Oct 2013 19:54:08 +0000

PROBLEM

You are getting this exception when invoking a web service:-

org.springframework.ws.client.WebServiceTransportException: Cannot process the message because the content type ‘application/soap+xml; charset=utf-8’ was not the expected type ‘text/xml; charset=utf-8’. [415]

SOLUTION

You are using the wrong SOAP version. SOAP v1.1 uses text/xml while SOAP v1.2 uses application/soap+xml.

If you are using Spring Web Services, add the following lines:-

The post Cannot process the message because the content type ‘application/soap+xml; charset=utf-8’ was not the expected type ‘text/xml; charset=utf-8’ appeared first on My Shitty Code.

Using Spring Web Services and JAXB to Invoke Web Service Based on WSDL

Shitty Author — Tue, 01 Oct 2013 13:17:11 +0000

There are several ways to consume a web service based on a WSDL from Java. After trying a couple of approaches, I’m currently leaning towards Spring Web Services and JAXB. The biggest advantage of using both Spring Web Services and JAXB to consume a web service is the flexibility to change the web service URL without the need to regenerate the needed Java files, especially if you have a different web service URL for each environment (DEV, TEST and PROD).

In this tutorial, I’m going to consume this freely available web service that allows me to convert the currency rate from one country to another: http://www.webservicex.net/CurrencyConvertor.asmx?WSDL

currency.wsdl ( src/main/resources )

The first step is to open the WSDL link on the browser and save a copy of it. In this example, I’m saving it as currency.wsdl.

Your project structure should look something like this:-

myproject
|- src
|  |- main
|     |- java
|     |  |- myproject
|     |- resources
|        |- currency.wsdl
|- pom.xml

pom.xml

Add Spring Web Services dependency and configure JAXB-2 Maven plugin to generate the Java files based on the WSDL.


	...
	
	    
	        org.springframework.ws
	        spring-ws-core
	        2.1.2.RELEASE
	    
	

    
        
			...

            
                org.codehaus.mojo
                jaxb2-maven-plugin
                1.5
                
                    
                        xjc
                        
                            xjc
                        
                    
                
                
					
                    myproject.wsdl.currency
					
                    true
                    
					false
                    
                    currency.wsdl
                    
					${project.basedir}/src/main/resources
                    
					${project.basedir}/src/main/java
                    
                    false

Setting clearOutputDir to false is very important. If this is set to true and there’s a silly error in the JAXB-2 Maven plugin configuration, your output directory will be wiped clean. Since the output directory points to ${project.basedir}/src/main/java, we want to make sure we don’t lose all of our existing Java files.

Generating Java Files Based on WSDL

While you can run mvn clean jaxb2:xjc to generate the Java files, the easier way is to just run mvn clean compile. You should see a similar Maven output in your console:-

[INFO] ------------------------------------------------------------------------
[INFO] Building myproject 1.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- jaxb2-maven-plugin:1.5:xjc (xjc) @ myproject ---
[INFO] Generating source...
[INFO] parsing a schema...
[INFO] compiling a schema...
[INFO] myproject/wsdl/currency/ConversionRate.java
[INFO] myproject/wsdl/currency/ConversionRateResponse.java
[INFO] myproject/wsdl/currency/Currency.java
[INFO] myproject/wsdl/currency/ObjectFactory.java
[INFO] myproject/wsdl/currency/package-info.java
[INFO]

Your project structure should look something like this:-

myproject
|- src
|  |- main
|     |- java
|     |  |- myproject
|     |     |- wsdl
|     |        |- currency
|     |           |- ConversionRate.java
|     |           |- ConversionRateResponse.java
|     |           |- Currency.java
|     |           |- ObjectFactory.java
|     |           |- package-info.java
|     |- resources
|        |- currency.wsdl
|- pom.xml

applicationContext.xml ( src/main/resources )

Once we have the generated Java files, the next step is to configure Spring Web Services.

CurrentService.java ( src/main/java/myproject/service )

In the Service class, we will use Spring Web Services WebServiceTemplate to call the web service.

@Service
public class CurrencyService {
    @Autowired
    private WebServiceTemplate webServiceTemplate;

    public Double getConversionRate(Currency fromCurrency, Currency toCurrency) {
        ConversionRate conversionRate = new ObjectFactory().createConversionRate();
        conversionRate.setFromCurrency(fromCurrency);
        conversionRate.setToCurrency(toCurrency);

        ConversionRateResponse response = (ConversionRateResponse) webServiceTemplate.marshalSendAndReceive(
                conversionRate);

        return response.getConversionRateResult();
    }
}

Main.java ( src/main/java/myproject/main )

This is the main runner class.

public class Main {
    private static Logger log = Logger.getLogger(Main.class);

    public static void main(String[] args) {
        ApplicationContext context = new ClassPathXmlApplicationContext("applicationContext.xml");
        CurrencyService currencyService = context.getBean(CurrencyService.class);

        Currency fromCurrency = Currency.USD;
        Currency toCurrency = Currency.GBP;
        Double conversionRate = currencyService.getConversionRate(fromCurrency, toCurrency);

        log.info(String.format("The conversion rate from %s to %s is %s.", fromCurrency, toCurrency, conversionRate));
    }
}

Project Structure

Your project structure should look something like this:-

myproject
|- src
|  |- main
|     |- java
|     |  |- myproject
|     |     |- main
|     |        |- Main.java
|     |     |- service
|     |        |- CurrencyService.java
|     |     |- wsdl
|     |        |- currency
|     |           |- ConversionRate.java
|     |           |- ConversionRateResponse.java
|     |           |- Currency.java
|     |           |- ObjectFactory.java
|     |           |- package-info.java
|     |- resources
|        |- currency.wsdl
|- pom.xml

Result

When you run Main.java, you should see a result similar to this:-

The conversion rate from USD to GBP is 0.6178.

The post Using Spring Web Services and JAXB to Invoke Web Service Based on WSDL appeared first on My Shitty Code.