Skip to content

Conversation

artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-4523

  • Change the LambdaMessageProcessor to rely on the MessageConverter
    populated by the IntegrationContextUtils.ARGUMENT_RESOLVER_MESSAGE_CONVERTER_BEAN_NAME
    This way all the Lambda-based handlers are going to work the same way
    as POJO-based via MessagingMethodInvokerHelper
  • Add convert(Class<P> payloadType) EIP-operator to perform similar
    to POJO-based method invocation argument conversion

@garyrussell
Copy link
Contributor

There are travis failures.

JIRA: https://jira.spring.io/browse/INT-4523

* Change the `LambdaMessageProcessor` to rely on the `MessageConverter`
populated by the `IntegrationContextUtils.ARGUMENT_RESOLVER_MESSAGE_CONVERTER_BEAN_NAME`
This way all the Lambda-based handlers are going to work the same way
as POJO-based via `MessagingMethodInvokerHelper`
* Add `convert(Class<P> payloadType)` EIP-operator to perform similar
to POJO-based method invocation argument conversion
`ConfigurableCompositeMessageConverter` from the mocked `BeanFactory`
* Make a `mappingJackson2MessageConverter.setStrictContentTypeMatch(true)`
* Also obtain an `ObjectMapper` from the `Jackson2JsonObjectMapper`
which is configured with the scanned possible Jackson modules.
in the `ConfigurableCompositeMessageConverter` do not try to convert
all the potential content without an appropriate JSON content-type
header
@garyrussell garyrussell merged commit 54094da into spring-projects:master Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants