You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Andreas Asmuss (JIRA)" <ji...@apache.org> on 2010/03/17 14:59:46 UTC

[jira] Created: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
-----------------------------------------------------------------------------------------------

                 Key: CAMEL-2555
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
            Reporter: Andreas Asmuss
            Priority: Minor
             Fix For: 2.3.0


When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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


[jira] Commented: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58939#action_58939 ] 

Claus Ibsen commented on CAMEL-2555:
------------------------------------

trunk: 935469.

Need to update wiki pages when they are working again

> When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2555
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Andreas Asmuss
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.3.0
>
>   Original Estimate: 5 hours
>  Remaining Estimate: 5 hours
>
> When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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


[jira] Commented: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58933#action_58933 ] 

Claus Ibsen commented on CAMEL-2555:
------------------------------------

This is a bit similar to pollEnrich where you want to access data from the old exchange, such as headers, which you can use the pollEnrich endpoint uri.



> When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2555
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Andreas Asmuss
>            Priority: Minor
>             Fix For: 2.3.0
>
>   Original Estimate: 5 hours
>  Remaining Estimate: 5 hours
>
> When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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


[jira] Resolved: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

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

Claus Ibsen resolved CAMEL-2555.
--------------------------------

    Resolution: Fixed

Updated wiki page.

Notice that in 2.3 onwards the wire tap will by default use a copy of the original tapped Exchange.

> When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2555
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Andreas Asmuss
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.3.0
>
>   Original Estimate: 5 hours
>  Remaining Estimate: 5 hours
>
> When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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


[jira] Assigned: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

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

Claus Ibsen reassigned CAMEL-2555:
----------------------------------

    Assignee: Claus Ibsen

> When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2555
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Andreas Asmuss
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.3.0
>
>   Original Estimate: 5 hours
>  Remaining Estimate: 5 hours
>
> When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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


[jira] Commented: (CAMEL-2555) When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58934#action_58934 ] 

Claus Ibsen commented on CAMEL-2555:
------------------------------------

This one will require some new API to provide the old exchange as {{Processor}} or {{Expression}} does not have 2 exchanges in their API.
We could also maybe have the old Exchange as a property on the new Exchange which you can fetch.

> When "Sending a new Exchange" with .wireTap() it should be possible to access the old exchange.
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2555
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2555
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Andreas Asmuss
>            Priority: Minor
>             Fix For: 2.3.0
>
>   Original Estimate: 5 hours
>  Remaining Estimate: 5 hours
>
> When using wireTap to create a new exchange the old exchange that spawns the wireTap is not around anymore. It could be useful to still be able to access the old exchange.

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