From 1851aaf2b087bcbe17d17965e656e942124d2370 Mon Sep 17 00:00:00 2001 From: Tomasz Kopczynski Date: Fri, 5 May 2017 11:42:07 +0200 Subject: [PATCH] Additional linking between sections in REST Docs integration documentation (#291) --- docs/src/main/asciidoc/spring-cloud-wiremock.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc index 8e80571029..081920b18c 100644 --- a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc +++ b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc @@ -288,8 +288,9 @@ will generate a stub something like this: NOTE: You can use either the `wiremock()` method or the `jsonPath()` and `contentType()` methods to create request matchers, but not both. -On the consumer side, assuming the `resource.json` generated above is -available on the classpath, you can create a stub using WireMock in a +On the consumer side, you can make the `resource.json` generated above +available on the classpath (by https://cloud.spring.io/spring-cloud-contract/1.0.x/#_publishing_stubs_as_jars[publishing stubs as JARs] for example). +After that, you can create a stub using WireMock in a number of different ways, including as described above using `@AutoConfigureWireMock(stubs="classpath:resource.json")`.