[CAMEL-6039] camel-bindy fixed length record improvements

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.11.0
• Fix Version/s: 2.11.0
• Component/s: camel-bindy
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Rich Newcomb
• Created: 06/Feb/13 07:06
• Updated: 28/Feb/13 05:57
• Resolved: 28/Feb/13 05:56

Description

The attached patch provides the following improvements for the camel-bindy fixed length record data format:

• full support for fixed-length header and footer records
• allows delimited (variable length) fields to be defined within "fixed-length" records
• enables the length of a data field to be defined dynamically by another field in the same record
• fixed-length records can be defined using ordinal / relative pos values

New annotation properties:
------------------
@DataField
+ lengthPos (int) – Optionally identifies a data field in the record that defines the fixed length for this field
+ delimiter (String) – Optional delimiter to be used if this field has a variable length

@FixedLengthRecord
+ hasHeader (boolean) – Indicates that the record(s) of this type may be preceded by a single header record at the beginning of the file / stream
+ hasFooter (boolean) – Indicates that the record(s) of this type may be followed by a single footer record at the end of the file / stream
+ skipHeader (boolean) – Configures the data format to skip marshalling / unmarshalling of the header record
+ skipFooter (boolean) – Configures the data format to skip marshalling / unmarshalling of the footer record
+ isHeader (boolean) – Identifies this FixedLengthRecord as a header record
+ isFooter (boolean) – Identifies this FixedLengthRecord as a footer record