[
https://issues.apache.org/jira/browse/CAMEL-11932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241586#comment-16241586
]
ASF GitHub Bot commented on CAMEL-11932:
----------------------------------------
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/2082
CAMEL-11932 - add new option for fixedlengthcvs unmarshalling because…
… Scanner is used and it needs delimiter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-11932
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2082.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 #2082
----
commit a6b3b19acca6234135b37bdd6a2b941606abc85f
Author: onders86 <[email protected]>
Date: 2017-11-07T06:37:46Z
CAMEL-11932 - add new option for fixedlengthcvs unmarshalling because
Scanner is used and it needs delimiter
----
> 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: Improvement
> Components: camel-bindy
> Affects Versions: 2.19.3
> Reporter: Marcin Domanski
> Assignee: Önder Sezgin
> 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)