SpringCloud/spring-cloud-contract
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Sync docs from master to gh-pages

Browse Source
This commit is contained in:
buildmaster
2019-01-08 14:27:22 +00:00
parent c2499c85bf
commit 400ce44917
3 changed files with 18 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
multi/multi__using_the_pluggable_architecture.html
View File

File diff suppressed because one or more lines are too long

8
single/spring-cloud-contract.html
View File

File diff suppressed because one or more lines are too long

8
spring-cloud-contract.xml
View File

@@ -9354,6 +9354,14 @@ Spring Cloud Contract currently only supports multiple matchers that are combine
Next to that the request and path matchers are skipped during the conversion.
When using a date, time or datetime value generator with a given format,
the given format will be skipped and the ISO format will be used.</simpara>
<simpara>In order to properly support the Spring Cloud Contract way of doing messaging
with Pact you&#8217;ll have to provide some additional meta data entries. Below you can find a list of such entries:</simpara>
<itemizedlist>
<listitem>
<simpara>to define the destination to which a message gets sent, you have to
set a <literal>metaData</literal> entry in the Pact file, with key <literal>sentTo</literal> equal to the destination to which a message is to be sent. E.g. <literal>"metaData": { "sentTo": "activemq:output" }</literal></simpara>
</listitem>
</itemizedlist>
</section>
<section xml:id="_pact_contract">
<title>Pact Contract</title>