According to my understanding Bindy FixedLengthRecord Object lets you define each field/property of the object with @DataField annotation. In @DataField annotation see the documentation as follows:
@DataField annotaion: "An annotation used to identify in a POJO which property is link to a field of a record (csv, ...). *The pos (mandatory)* identifies the position of the data in the record ........" So basically in case of recurring data , IMHO we need to have explicit mapping logic as explained earlier. in your case the following defination of object..has to have @DataField with 'pos' (mandatory) and it is defined upfront in your java class. eg: @DataField(pos = (151), length = 2) String item1Property1; Again these are purely my personal opinions, please stay tuned for any other ideas from other users in the forum. If you feel any improvements that can be made to Bindy parser as such please raise the Jira with description , based on the track record I am sure they will address it in timely fashion. peace, surya -- View this message in context: http://camel.465427.n5.nabble.com/FixedLengthRecord-and-OneToMany-tp5571433p5577214.html Sent from the Camel - Users mailing list archive at Nabble.com.
