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

Claus Ibsen commented on CAMEL-6039:
------------------------------------

Thanks Rich for the patch. I have applied it to trunk.

Fell free to improved the docs, and add a note to the 2.11 release notes about 
this great new improvements to camel-bindy.

Btw you are most welcome to take a look at the other bindy tickets we have 
logged. For example there is a ticket about the issue with bindy not liking to 
have multiple root objects in the same java package. There is a ticket logged a 
about that.
                
> camel-bindy fixed length record improvements
> --------------------------------------------
>
>                 Key: CAMEL-6039
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6039
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-bindy
>    Affects Versions: 2.11.0
>            Reporter: Rich Newcomb
>             Fix For: 2.11.0
>
>         Attachments: CAMEL-6039.patch
>
>
> 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 
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to