You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #18343, we should consider extracting our message abstraction payload lazily, since it might not be needed at all for a given endpoint. The place to do this would be MessagingMessageConverter.fromMessage, using a to-be-introduced lazy variant of MessageBuilder.withPayload with a callback that calls extractPayload on demand.
Juergen Hoeller opened SPR-13777 and commented
Following up on #18343, we should consider extracting our message abstraction payload lazily, since it might not be needed at all for a given endpoint. The place to do this would be
MessagingMessageConverter.fromMessage
, using a to-be-introduced lazy variant ofMessageBuilder.withPayload
with a callback that callsextractPayload
on demand.Affects: 4.2.3
Issue Links:
Referenced from: commits b7a9364, 31a3607
The text was updated successfully, but these errors were encountered: