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 2010/06/02 06:04:52 UTC

[jira] Closed: (CAMEL-2777) Exchange get methods should not alter the object

     [ https://issues.apache.org/activemq/browse/CAMEL-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen closed CAMEL-2777.
------------------------------

    Resolution: Working as Designed

Please discuss this at the developer mailinglist.

We have debated this a lot. And this was how Camel was designed and inspired from JBI.
You can use the hasOut to detect if an OUT message has been set.


> Exchange get methods should not alter the object
> ------------------------------------------------
>
>                 Key: CAMEL-2777
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2777
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: Roland Knight
>            Priority: Minor
>
> The get methods such as getOut() should not modify (or change the behaviour) of the Exchange object. For example simply by invoking getOut(), the behaviour of the next step is changed since the out object is created (and is empty - causing a blow up!). This is very easy to do when turning on debugging or inspecting/watching variables.

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