[jira] [Commented] (CAMEL-11932) For fixed length records crlf field is not honored during un-marshaling

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-11932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237244#comment-16237244 ] 

Claus Ibsen commented on CAMEL-11932:
-------------------------------------

What is your use-case - it reads the file using the default JDK Scanner which supports line breaks on all known OS'es and therefore IMHO is more capable of reading files from windows, unix, mac etc without trouble.

> For fixed length records crlf field is not honored during un-marshaling 
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-11932
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11932
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-bindy
>    Affects Versions: 2.19.3
>            Reporter: Marcin Domanski
>            Priority: Minor
>
> Reading documentation [here|http://camel.apache.org/bindy.html] you can find that there is a {{@FixedLengthRecord.clrf}} annotation parameter described as:
> bq. optional - possible values = WINDOWS,UNIX,MAC, or custom; default value = WINDOWS - allow to define the carriage return character to use. If you specify a value other than the three listed before, the value you enter (custom) will be used as the CRLF character(s)
> Unfortunately it seems that this is honored only for marshaling, as for un-marshaling in {{BindyFixedLengthDataFormat.unmarshal()}} java.util.Scanner.nextLine() is used. This implementation ignores the crlf parameter during un-marshaling.



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