Skip to content

Latest commit

 

History

History
178 lines (141 loc) · 6.95 KB

README.md

File metadata and controls

178 lines (141 loc) · 6.95 KB
Raw

SOAP WS Addressing sample Logo

This sample uses SOAP web services with WSAddressing SOAP header elements. Clients must use proper addressing header elements. You can read more about the Citrus SOAP features in reference guide

Objectives

The sample project uses WSAddressing feature for requests sent to sample SOAP server. The Citrus SOAP web service server endpoint validates incoming requests and expects WSAddressing headers to be present in all requests.

First of all we add the WSAddressing header conversion to the client component.

@Bean
public WebServiceClient todoClient() {
    return CitrusEndpoints
        .soap()
            .client()
            .defaultUri("http://localhost:8080/services/ws/todolist")
            .messageConverter(wsAddressingMessageConverter())
        .build();
}

@Bean
public WebServiceMessageConverter wsAddressingMessageConverter() {
    WsAddressingHeaders addressingHeaders = new WsAddressingHeaders();

    addressingHeaders.setVersion(WsAddressingVersion.VERSION200408);
    addressingHeaders.setAction(URI.create("http://citrusframework.org/samples/todolist"));
    addressingHeaders.setTo(URI.create("http://citrusframework.org/samples/todolist"));

    addressingHeaders.setFrom(new EndpointReference(URI.create("http://citrusframework.org/samples/client")));
    addressingHeaders.setReplyTo(new EndpointReference(URI.create("http://citrusframework.org/samples/client")));
    addressingHeaders.setFaultTo(new EndpointReference(URI.create("http://citrusframework.org/samples/client/fault")));

    return new WsAddressingMessageConverter(addressingHeaders);
}

The client message converter automatically adds WSAddressing headers to the SOAP header. The resulting request look as follows.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
        <wsa:To SOAP-ENV:mustUnderstand="1">http://citrusframework.org/samples/todolist</wsa:To>
        <wsa:From>
            <wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://citrusframework.org/samples/client</wsa:Address>
        </wsa:From>
        <wsa:ReplyTo>
            <wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://citrusframework.org/samples/client</wsa:Address>
        </wsa:ReplyTo>
        <wsa:FaultTo>
            <wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://citrusframework.org/samples/client</wsa:Address>
        </wsa:FaultTo>
        <wsa:Action>http://citrusframework.org/samples/todolist</wsa:Action>
        <wsa:MessageID>urn:uuid:a3975ef6-68f2-4074-b157-db6c230120b6</wsa:MessageID>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <todo:getTodoListRequest xmlns:todo="http://citrusframework.org/samples/todolist">
        </todo:getTodoListRequest>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The WSAddressing information goes to the header section and contains several elements. One of the elements is marked as SOAP-ENV:mustUnderstand.

The server component has to add the SOAP-ENV:mustUnderstand handling explicitly in order to support the incoming WSAddressing headers:

@Bean
public WebServiceServer todoListServer() {
    return CitrusEndpoints
        .soap()
            .server()
            .autoStart(true)
            .port(8080)
            .interceptors(serverInterceptors())
        .build();
}

@Bean
public List<EndpointInterceptor> serverInterceptors() {
    return Arrays.asList(soapMustUnderstandEndpointInterceptor(), new LoggingEndpointInterceptor());
}

@Bean
public EndpointInterceptor soapMustUnderstandEndpointInterceptor() {
    SoapMustUnderstandEndpointInterceptor interceptor = new SoapMustUnderstandEndpointInterceptor();
    interceptor.setAcceptedHeaders(Collections.singletonList("{http://schemas.xmlsoap.org/ws/2004/08/addressing}To"));
    return interceptor;
}

The server is now ready to receive the request and validate the WSAddressing header information.

$(soap()
    .server(todoServer)
    .receive()
    .body(new ClassPathResource("templates/addTodoEntryRequest.xml"))
    .header(new ClassPathResource("templates/soapWsAddressingHeader.xml")));

$(soap()
    .server(todoServer)
    .send()
    .body(new ClassPathResource("templates/addTodoEntryResponse.xml")));

We do this by adding the complete SOAP header as expected XML structure. The header information is loaded from external file resource.

<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
  <wsa:To SOAP-ENV:mustUnderstand="1">http://citrusframework.org/samples/todolist</wsa:To>
  <wsa:From>
    <wsa:Address>http://citrusframework.org/samples/client</wsa:Address>
  </wsa:From>
  <wsa:ReplyTo>
    <wsa:Address>http://citrusframework.org/samples/client</wsa:Address>
  </wsa:ReplyTo>
  <wsa:FaultTo>
    <wsa:Address>http://citrusframework.org/samples/client</wsa:Address>
  </wsa:FaultTo>
  <wsa:Action>http://citrusframework.org/samples/todolist</wsa:Action>
  <wsa:MessageID>@ignore@</wsa:MessageID>
</SOAP-ENV:Header>

Citrus automatically performs XML comparison and validation on all header elements. As you can see we ignore the MessageID element with @ignore@. This is simply because this is a generated UUID value that is newly generated on the client side for each request.

In general we can overwrite WSAddressing header information in each send operation by setting the special WSAddressing message headers.

$(soap()
    .client(todoClient)
    .send()
    .soapAction("addTodoEntry")
    .header(WsAddressingMessageHeaders.ACTION, "http://citrusframework.org/samples/todolist/addTodoEntry")
    .header(WsAddressingMessageHeaders.MESSAGE_ID, "urn:uuid:citrus:randomUUID()")
    .body(new ClassPathResource("templates/addTodoEntryRequest.xml")));

Run

The sample application uses Maven as build tool. So you can compile, package and test the sample with Maven.

 mvn clean install

This executes the complete Maven build lifecycle. During the build you will see Citrus performing some integration tests.

Execute all Citrus tests by calling

 mvn verify

You can also pick a single test by calling

 mvn verify -Dit.test=<testname>

You should see Citrus performing several tests with lots of debugging output. And of course green tests at the very end of the build.

Of course you can also start the Citrus tests from your favorite IDE. Just start the Citrus test using the TestNG IDE integration in IntelliJ, Eclipse or Netbeans.

Further information

For more information on Citrus see www.citrusframework.org, including a complete reference manual.