You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/01/04 12:47:05 UTC

[jira] Created: (CAMEL-1222) DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery

DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery
----------------------------------------------------------------------------------------

                 Key: CAMEL-1222
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1222
             Project: Apache Camel
          Issue Type: New Feature
          Components: camel-core
            Reporter: Claus Ibsen
             Fix For: 2.0.0


This ticket is created to not forget about this and get a discussion going.

When Camel handles redeliver using DLC for processors (org.apache.camel.Processor) and bean invocations (only in the special case where it operates directly on the Exchange = Exchange as parameter), then any changes that was done before is also present at the next redelivery attempt.
So for instance changing the body value, or adding a header etc. will cause these changes on the Exchange.

We should document this - especially for org.apache.camel.Processor. bean component end users is encouraged to use bean binding, that hasn't this issue (except for Headers, Properties).



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (CAMEL-1222) DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-1222:
-------------------------------

    Issue Type: Improvement  (was: New Feature)

> DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery
> ----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1222
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1222
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>             Fix For: 2.0.0
>
>
> This ticket is created to not forget about this and get a discussion going.
> When Camel handles redeliver using DLC for processors (org.apache.camel.Processor) and bean invocations (only in the special case where it operates directly on the Exchange = Exchange as parameter), then any changes that was done before is also present at the next redelivery attempt.
> So for instance changing the body value, or adding a header etc. will cause these changes on the Exchange.
> We should document this - especially for org.apache.camel.Processor. bean component end users is encouraged to use bean binding, that hasn't this issue (except for Headers, Properties).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CAMEL-1222) DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-1222.
--------------------------------

    Resolution: Won't Fix

> DeadLetterChannel - Snapshots for processor and (bean invocations) when doing redelivery
> ----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1222
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1222
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>             Fix For: 2.0.0
>
>
> This ticket is created to not forget about this and get a discussion going.
> When Camel handles redeliver using DLC for processors (org.apache.camel.Processor) and bean invocations (only in the special case where it operates directly on the Exchange = Exchange as parameter), then any changes that was done before is also present at the next redelivery attempt.
> So for instance changing the body value, or adding a header etc. will cause these changes on the Exchange.
> We should document this - especially for org.apache.camel.Processor. bean component end users is encouraged to use bean binding, that hasn't this issue (except for Headers, Properties).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.