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

2017-12-14 Thread Claus Ibsen (JIRA)

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

Claus Ibsen updated CAMEL-12080:

Fix Version/s: Future

> 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)


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

2017-12-14 Thread Claus Ibsen (JIRA)

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

Claus Ibsen updated CAMEL-12080:

Estimated Complexity: Novice  (was: Unknown)

> 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)