[
https://issues.apache.org/jira/browse/CAMEL-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352532#comment-16352532
]
Claus Ibsen commented on CAMEL-8958:
------------------------------------
So I have pushed a prototype of this in a new native EIP implementation of the
Claim Check EIP pattern from the EIP book. I think this functionality closely
resemble this EIP pattern.
There is still a bit naming to be decided. You need to specify what operation
to use: push, pop, and there is also a get/set etc. I do think I would like to
rename the option operation to action instead.
You can find some details of the implementation and its limitation in the class
javadoc for the ClaimCheckProcessor class.
The documentation is at:
https://github.com/apache/camel/blob/8958/camel-core/src/main/docs/eips/claimCheck-eip.adoc
The branch
https://github.com/apache/camel/tree/8958
> Add push/pop to the DSL so people can easily preserve and get back a message
> as-is
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-8958
> URL: https://issues.apache.org/jira/browse/CAMEL-8958
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.21.0
>
>
> We may ponder about some good naming for an EIP that remembers an Exchange
> and then allow to restore that Exchange at a later point.
> We could have push/pop as a stack fashion. Or use some kind of naming,
> push(foo) and then pop(foo). Or some better naming.
> People today have stored the message body as an exchange body and then
> restored that later. But this may be simpler.
> For pop we could allow an optional aggregation strategy so people can merge
> the current exchange with the pop in any way they want.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
