From 8f176ab2b75f9a4552ee6ec5dfbb910a7546f590 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Mon, 18 Jun 2018 11:39:50 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__spring_cloud_contract_verifier_messaging.html | 6 +++--- single/spring-cloud-contract.html | 6 +++--- spring-cloud-contract.xml | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/multi/multi__spring_cloud_contract_verifier_messaging.html b/multi/multi__spring_cloud_contract_verifier_messaging.html index 4cdad5f35d..862d472514 100644 --- a/multi/multi__spring_cloud_contract_verifier_messaging.html +++ b/multi/multi__spring_cloud_contract_verifier_messaging.html @@ -35,7 +35,7 @@ message is triggered by a component inside the application (for example, schedu meanings for different messaging implementations. For Stream and Integration it is first resolved as a destination of a channel. Then, if there is no such destination it is resolved as a channel name. For Camel, that’s a certain component (for example, -jms).

5.3.1 Scenario 1: No Input Message

Here is an example for Camel. For the given contract:

Groovy DSL.  +jms).

5.3.1 Scenario 1: No Input Message

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
@@ -88,7 +88,7 @@ outputMessage:
   DocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.payload))
   assertThatJson(parsedJson).field("bookName").isEqualTo("foo")
 
-'''

5.3.2 Scenario 2: Output Triggered by Input

Here is an example for Camel. For the given contract:

Groovy DSL.  +'''

5.3.2 Scenario 2: Output Triggered by Input

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
@@ -159,7 +159,7 @@ then:
 and:
    DocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.payload))
    assertThatJson(parsedJson).field("bookName").isEqualTo("foo")
-"""

5.3.3 Scenario 3: No Output Message

Here is an example for Camel. For the given contract:

Groovy DSL.  +"""

5.3.3 Scenario 3: No Output Message

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
diff --git a/single/spring-cloud-contract.html b/single/spring-cloud-contract.html
index 32b5aeaf47..f5a125386d 100644
--- a/single/spring-cloud-contract.html
+++ b/single/spring-cloud-contract.html
@@ -2151,7 +2151,7 @@ message  is triggered by a component inside the application (for example, schedu
 meanings for different messaging implementations. For Stream and Integration it is
 first resolved as a destination of a channel. Then, if there is no such destination
 it is resolved as a channel name. For Camel, that’s a certain component (for example,
-jms).

5.3.1 Scenario 1: No Input Message

Here is an example for Camel. For the given contract:

Groovy DSL.  +jms).

5.3.1 Scenario 1: No Input Message

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
@@ -2204,7 +2204,7 @@ outputMessage:
   DocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.payload))
   assertThatJson(parsedJson).field("bookName").isEqualTo("foo")
 
-'''

5.3.2 Scenario 2: Output Triggered by Input

Here is an example for Camel. For the given contract:

Groovy DSL.  +'''

5.3.2 Scenario 2: Output Triggered by Input

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
@@ -2275,7 +2275,7 @@ then:
 and:
    DocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.payload))
    assertThatJson(parsedJson).field("bookName").isEqualTo("foo")
-"""

5.3.3 Scenario 3: No Output Message

Here is an example for Camel. For the given contract:

Groovy DSL.  +"""

5.3.3 Scenario 3: No Output Message

For the given contract:

Groovy DSL.  

def contractDsl = Contract.make {
 	label 'some_label'
 	input {
diff --git a/spring-cloud-contract.xml b/spring-cloud-contract.xml
index e4fc02d4aa..74537e86e4 100644
--- a/spring-cloud-contract.xml
+++ b/spring-cloud-contract.xml
@@ -3789,7 +3789,7 @@ it is resolved as a channel name. For Camel,
 
 

 Scenario 1: No Input Message
-Here is an example for Camel. For the given contract:
+For the given contract:
 
 Groovy DSL
 
@@ -3858,7 +3858,7 @@ outputMessage:
 

 

 Scenario 2: Output Triggered by Input
-Here is an example for Camel. For the given contract:
+For the given contract:
 
 Groovy DSL
 
@@ -3945,7 +3945,7 @@ and:
 

 

 Scenario 3: No Output Message
-Here is an example for Camel. For the given contract:
+For the given contract:
 
 Groovy DSL