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] Commented: (CAMEL-1563) Message - getOut, getFault should not create empty message if none exists
Date Tue, 28 Apr 2009 15:21:40 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51422#action_51422
] 

Claus Ibsen commented on CAMEL-1563:
------------------------------------

Thanks Roman. I am on the same level as you. Would love the Exchange API to be simpler, but
it was afterall inherited from the JBI world :)

What we are currently implementing is
- hasOut()
- hasFault()

{code}
System.out.println(exchange.getIn());
if (exchange.hasOut()) }
    System.out.println(exchange.getOut());
}
{code}



> 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