camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1563) Message - getOut, getFault should not create empty message if none exists
Date Mon, 18 May 2009 06:10:50 GMT

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

Claus Ibsen resolved CAMEL-1563.
--------------------------------

    Resolution: Fixed

We end with the compromise.

End users can use {{hasOut()}} to test whether an OUT message has been set.
The {{getOut()}} method does as it have always done, lazy creating one if missing.

To much code depends on this behavior.




> Message - getOut, getFault should not create empty message if none exists
> -------------------------------------------------------------------------
>
>                 Key: CAMEL-1563
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1563
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>
> The getOut and getFault methods on org.apache.camel.Message creates a new empty object
if none exists already.
> This confuses end users when they use the methods in their custom processors.
> We should instead add hasOut, hasFault methods that can be used for checking if it exists
or not.
> *Note:* The getOut(false) can be used to not create a new message if none exists but
its really not adhering to good java beans standard.
> See nabble:
> http://www.nabble.com/Payload-Gets-Nulled-Out-td23105477.html

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


Mime
View raw message