[
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291895#comment-16291895
]
ASF GitHub Bot commented on CAMEL-12080:
----------------------------------------
GitHub user ricardozanini opened a pull request:
https://github.com/apache/camel/pull/2149
CAMEL-12080: allow creating csvcontent without last eol
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ricardozanini/camel camel-12080
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2149.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2149
----
commit 156371bb83923249ce2f060a31f378e8db7e48bf
Author: Ricardo Zanini <ricardozan...@gmail.com>
Date: 2017-12-15T01:28:29Z
CAMEL-12080: allow creating csvcontent without last eol
----
> 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
> Priority: Minor
> Fix For: Future
>
>
> 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)
