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/04/28 11:54:39 UTC
[jira] Assigned: (CAMEL-1563) Message - getOut, getFault should not
create empty message if none exists
[ https://issues.apache.org/activemq/browse/CAMEL-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-1563:
----------------------------------
Assignee: Claus Ibsen
> 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.