From 0b9d164554e797df41d0b62712431a537fb42b11 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Thu, 4 Nov 2010 12:45:50 +0000 Subject: [PATCH] javadoc --- .../springframework/ws/test/client/MockWebServiceServer.java | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/test/src/main/java/org/springframework/ws/test/client/MockWebServiceServer.java b/test/src/main/java/org/springframework/ws/test/client/MockWebServiceServer.java index 1dfdbce0..b838d72e 100644 --- a/test/src/main/java/org/springframework/ws/test/client/MockWebServiceServer.java +++ b/test/src/main/java/org/springframework/ws/test/client/MockWebServiceServer.java @@ -30,9 +30,8 @@ import org.springframework.ws.test.support.MockStrategiesHelper; * The typical usage of this class is: *
    *
  1. Create a {@code MockWebServiceServer} instance by calling {@link #createServer(WebServiceTemplate)}, + * {@link #createServer(WebServiceGatewaySupport)}, or {@link #createServer(ApplicationContext)}. * or any other the other {@code createServer()} methods. - * Typically, the template is configured as a Spring bean, either explicitly or as a property of a class that extends - * {@link WebServiceGatewaySupport WebServiceGatewaySupport}.
    2. *
  2. Set up request expectations by calling {@link #expect(RequestMatcher)}, possibly by using the default * {@link RequestMatcher} implementations provided in {@link RequestMatchers} (which can be statically imported). * Multiple expectations can be set up by chaining {@link ResponseActions#andExpect(RequestMatcher)} calls.