From 7daa56472a6a40c92669246d077dd592f8b2be9b Mon Sep 17 00:00:00 2001
From: buildmaster
Date: Wed, 10 May 2017 08:49:28 +0000
Subject: [PATCH] Sync docs from 1.0.x to gh-pages
---
1.0.x/spring-cloud-contract.html | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/1.0.x/spring-cloud-contract.html b/1.0.x/spring-cloud-contract.html
index d17c6b9693..0e55ff5d3d 100644
--- a/1.0.x/spring-cloud-contract.html
+++ b/1.0.x/spring-cloud-contract.html
@@ -1273,6 +1273,13 @@ number of different ways, including as described above using
Contract DSL file and documentation. If you combine that with Spring Cloud
WireMock then you’re getting both the contracts and stubs.
+
+
Why would you want to use this feature? Some people in the community asked questions
+about situation in which they would like to move to DSL based contract definition
+but they already have a lot of Spring MVC tests. Using this feature allows you to generate
+the contract files that you can later modify and move to proper folders so that the
+plugin picks them up.
+
@@ -1322,15 +1329,13 @@ section, contract will get generated and a documentation file too.
Contract.make {
request {
method 'POST'
- url 'http://localhost:8080/foo'
+ url '/foo'
body('''
{"foo": 23 }
''')
headers {
header('''Accept''', '''application/json''')
header('''Content-Type''', '''application/json''')
- header('''Host''', '''localhost:8080''')
- header('''Content-Length''', '''12''')
}
}
response {