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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.19.3
• Fix Version/s: 2.19.5, 2.20.1, 2.21.0
• Component/s: camel-bindy
• Estimated Complexity: Unknown
• Assignee: Onder Sezgin
• Reporter: Marcin Domanski
• Created: 20/Oct/17 15:14
• Updated: 13/Nov/17 18:29
• Resolved: 08/Nov/17 13:57

Description

Reading documentation here you can find that there is a @FixedLengthRecord.clrf annotation parameter described as:

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.

Issue Links

• links to: GitHub Pull Request #2082
• links to: GitHub Pull Request #2082