You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/03/22 17:54:25 UTC

[jira] [Resolved] (CAMEL-9745) Splitter - Should skip null messages if iterator returns null

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

Claus Ibsen resolved CAMEL-9745.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.16.3

> Splitter - Should skip null messages if iterator returns null
> -------------------------------------------------------------
>
>                 Key: CAMEL-9745
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9745
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.16.2
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.16.3, 2.18.0, 2.17.1
>
>
> When splitting and using an iterator the usually hasNext -> next is paired so if hasNext returns true, then next returns data. But there can be situations where this is tricky to determine up front, and therefore a hasNext may return true, and then next() return null if there was no data really. Then the splitter should just skip that null and continue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)