From 38eafa3490986b13c39c40018d86e35270ffb64a Mon Sep 17 00:00:00 2001 From: voytech Date: Tue, 28 Jul 2020 09:27:42 +0200 Subject: [PATCH] Minor modification in docs. Fix gh-410. --- docs/src/main/asciidoc/spring-cloud-aws.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-aws.adoc b/docs/src/main/asciidoc/spring-cloud-aws.adoc index ff639eee6f..e9b38c00b2 100644 --- a/docs/src/main/asciidoc/spring-cloud-aws.adoc +++ b/docs/src/main/asciidoc/spring-cloud-aws.adoc @@ -1130,10 +1130,9 @@ annotations. `@Header` is used to inject a specific header value while `@Headers containing all headers. Only the link:https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_Message.html[standard -message attributes] sent with an SQS message are fully supported. Custom attributes are handled only partially. -Custom message attribute value is resolved only by using mandatory type part without custom label (type name without label after '.') -Custom type label is skipped during conversion to header value. -(You can still access original message and custom labels using `sourceData` message header) +message attributes] sent with an SQS message are fully supported. +Custom message attribute are handled as if custom type label (everything after '.' in type name) wasn't present in attribute key. +It is silently omitted during conversion, but still can be accessed as long as original message is present in 'sourceData' header. In addition to the provided argument resolvers, custom ones can be registered on the `aws-messaging:annotation-driven-queue-listener` element using the `aws-messaging:argument-resolvers` attribute (see example below).