You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Nicky Sandhu (JIRA)" <ji...@apache.org> on 2007/09/27 01:50:23 UTC

[jira] Created: (CAMEL-160) TryProcessor does not process finally if no catch defined

TryProcessor does not process finally if no catch defined
---------------------------------------------------------

                 Key: CAMEL-160
                 URL: https://issues.apache.org/activemq/browse/CAMEL-160
             Project: Apache Camel
          Issue Type: Bug
            Reporter: Nicky Sandhu
            Assignee: James Strachan
         Attachments: patch.txt

try{}finally{} pattern does not work. There is also the problem (see test) of TryType getting lost ( a fluent API issue).

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


[jira] Commented: (CAMEL-160) TryProcessor does not process finally if no catch defined

Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40191 ] 

Nicky Sandhu commented on CAMEL-160:
------------------------------------

Attached a patch. I am not sure if on handleAll the dead letter handler should be disabled? However thats the implementation in the patch.

> TryProcessor does not process finally if no catch defined
> ---------------------------------------------------------
>
>                 Key: CAMEL-160
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-160
>             Project: Apache Camel
>          Issue Type: Bug
>            Reporter: Nicky Sandhu
>            Assignee: James Strachan
>         Attachments: patch.txt
>
>
> try{}finally{} pattern does not work. There is also the problem (see test) of TryType getting lost ( a fluent API issue).

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


[jira] Updated: (CAMEL-160) TryProcessor does not process finally if no catch defined

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

Nicky Sandhu updated CAMEL-160:
-------------------------------

    Attachment: patch.txt

> TryProcessor does not process finally if no catch defined
> ---------------------------------------------------------
>
>                 Key: CAMEL-160
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-160
>             Project: Apache Camel
>          Issue Type: Bug
>            Reporter: Nicky Sandhu
>            Assignee: James Strachan
>         Attachments: patch.txt
>
>
> try{}finally{} pattern does not work. There is also the problem (see test) of TryType getting lost ( a fluent API issue).

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


[jira] Resolved: (CAMEL-160) TryProcessor does not process finally if no catch defined

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

James Strachan resolved CAMEL-160.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

patch applied with huge thanks

> TryProcessor does not process finally if no catch defined
> ---------------------------------------------------------
>
>                 Key: CAMEL-160
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-160
>             Project: Apache Camel
>          Issue Type: Bug
>            Reporter: Nicky Sandhu
>            Assignee: James Strachan
>             Fix For: 1.2.0
>
>         Attachments: patch.txt
>
>
> try{}finally{} pattern does not work. There is also the problem (see test) of TryType getting lost ( a fluent API issue).

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