diff --git a/build.gradle b/build.gradle index d46d1639e0..49ad7e896f 100644 --- a/build.gradle +++ b/build.gradle @@ -9,7 +9,7 @@ buildscript { } dependencies { classpath 'org.springframework.build.gradle:bundlor-plugin:0.1.2-SNAPSHOT' - classpath 'org.springframework.build.gradle:docbook-reference-plugin:0.1.2-SNAPSHOT' + classpath 'org.springframework.build.gradle:docbook-reference-plugin:0.1.3' } } diff --git a/src/reference/docbook/claim-check.xml b/src/reference/docbook/claim-check.xml index e661a34f8f..90e87c1990 100644 --- a/src/reference/docbook/claim-check.xml +++ b/src/reference/docbook/claim-check.xml @@ -15,7 +15,7 @@ - The Claim Check pattern describes a mechanism that allows you + The Claim Check pattern describes a mechanism that allows you to store data in a well known place while only maintaining a pointer (Claim Check) to where that data is located. You can pass that pointer around as a payload of a new Message thereby allowing any component within the message flow to get the actual data as soon as it needs it. This approach is very similar to the Certified Mail process where you'll get a Claim Check in your mailbox and diff --git a/src/reference/docbook/content-enrichment.xml b/src/reference/docbook/content-enrichment.xml index c3429b0a8d..47655936a5 100644 --- a/src/reference/docbook/content-enrichment.xml +++ b/src/reference/docbook/content-enrichment.xml @@ -8,7 +8,7 @@ At times you may have a requirement to enhance a request with more information than was provided by the target system. The - Content Enricher + Content Enricher pattern describes various scenarios as well as the component (Enricher), which allows you to address such requirements. @@ -122,7 +122,7 @@ In Spring Integration 2.0 we have introduced the convenience of the - Spring Expression Language (SpEL) + Spring Expression Language (SpEL) to help configure many different components. The Header Enricher is one of them.