[jira] [Updated] (CAMEL-8958) Add push/pop to the DSL so people can easily preserve and get back a message as-is
[ https://issues.apache.org/jira/browse/CAMEL-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8958: --- Fix Version/s: (was: 2.22.0) (was: 3.0.0) 2.21.0 > 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)
[jira] [Updated] (CAMEL-8958) Add push/pop to the DSL so people can easily preserve and get back a message as-is
[ https://issues.apache.org/jira/browse/CAMEL-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8958: --- Fix Version/s: (was: Future) 2.22.0 > 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: 3.0.0, 2.22.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)
[jira] [Updated] (CAMEL-8958) Add push/pop to the DSL so people can easily preserve and get back a message as-is
[ https://issues.apache.org/jira/browse/CAMEL-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8958: --- Fix Version/s: 3.0.0 > 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 > Fix For: 3.0.0, Future > > > 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 (v6.4.14#64029)
