camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "onder sezgin (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CAMEL-7862) Allow empty csv files in the Camel Bindy unmarshalling process
Date Thu, 09 Mar 2017 13:12:37 GMT

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

onder sezgin reassigned CAMEL-7862:
-----------------------------------

    Assignee: onder sezgin

> Allow empty csv files in the Camel Bindy unmarshalling process
> --------------------------------------------------------------
>
>                 Key: CAMEL-7862
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7862
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-bindy
>            Reporter: Tom So
>            Assignee: onder sezgin
>            Priority: Minor
>
> Currently the unmarshal process of Camel Bindy will throw an IllegalArgumentException
if the provided data stream is empty. Therefore the client has to catch that Exception or
bypass the unmarshal process to handle empty files.
> It would be an improvement if Bindy will always return an empty collection if the data
stream is empty and there is nothing to unmarshal. Or if there is an annotation available
to decide how empty stream should be treated (i.e., throw an exception or return an empty
collection). The annotation could be part of the @CsvRecord annotation: @CsvRecord(allowEmptyFiles
= true).
> Please see this discussion on the camel users mailing list for further information: http://camel.465427.n5.nabble.com/Why-does-Bindy-prohibit-empty-files-td5756976.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message