This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch 8958 in repository https://gitbox.apache.org/repos/asf/camel.git
commit 11bcf97c4eb6cd1cbd049db560770882fb6904aa Author: Claus Ibsen <[email protected]> AuthorDate: Tue Feb 6 16:21:11 2018 +0100 CAMEL-8958: Claim Check EIP with push/pop. Work in progress. --- camel-core/src/main/docs/eips/claimCheck-eip.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/camel-core/src/main/docs/eips/claimCheck-eip.adoc b/camel-core/src/main/docs/eips/claimCheck-eip.adoc index 3b52ea2..b2f4593 100644 --- a/camel-core/src/main/docs/eips/claimCheck-eip.adoc +++ b/camel-core/src/main/docs/eips/claimCheck-eip.adoc @@ -3,8 +3,10 @@ *Available as of Camel 2.21* -The Claim Check EIP allows you to replace message content with a claim check (a unique key), -which can be used to retrieve the message content at a later time. +The link:http://www.enterpriseintegrationpatterns.com/patterns/messaging/StoreInLibrary.html[Claim Check] from the link:../../../../readme-eip.adoc[EIP patterns] +allows you to replace message content with a claim check (a unique key), which can be used to retrieve the message content at a later time. + +image:http://www.enterpriseintegrationpatterns.com/img/StoreInLibrary.gif[image] It can also be useful in situations where you cannot trust the information with an outside party; in this case, you can use the Claim Check to hide the sensitive portions of data. -- To stop receiving notification emails like this one, please contact [email protected].
