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 2017/12/15 09:40:00 UTC

[jira] [Resolved] (CAMEL-12080) Allow creating csv content without last eol

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

Claus Ibsen resolved CAMEL-12080.
---------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s:     (was: Future)
                   2.21.0

Thanks for the PR

> Allow creating csv content without last eol
> -------------------------------------------
>
>                 Key: CAMEL-12080
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12080
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-bindy
>            Reporter: Marcin Domanski
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.21.0
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization Bindy to my knowledge always creates content with last row ending with newline. Unfortunately some legacy systems treat last newline as one more empty row. Would it be possible to introduce control over this? I have this problem in CSV and also in fixed format for one other place. For now we need to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)