camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Resolved: (CAMEL-1857) Improvements to Flatpack DataFormat
Date Fri, 20 Nov 2009 07:42:54 GMT


Claus Ibsen resolved CAMEL-1857.

    Resolution: Won't Fix

Feature which is better implemented in flatpack. However flatpack is also a project which
seems not maintained anymore.

> Improvements to Flatpack DataFormat
> -----------------------------------
>                 Key: CAMEL-1857
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-flatpack
>    Affects Versions: 2.0-M1
>            Reporter: Yuri Schimke
>            Priority: Minor
> There are some small improvements that would improve the Flatpack DataFormat.  Basically
because the header and trailer are fixed names, and are not exposed via the DataSetList, there
are some cases where we need to write our own code instead of using the FlatPack DataFormat.
> Firstly, it would be good if instead of two special cases "header" and "trailer", if
you could designate your own set of special record ids to be checked e.g. "header", "footer1",
"footer2".  This would allow us to reuse our existing flatpack config files, especially where
we have most than one footer.
> Secondly, since the FlatpackConverter already detects the record id as part of its processing,
it would be nice if it included this as a synthetic key value in the DataSetList e.g. "record_type"
-> "trailer".  
> n.b. I have raised a feature request with FlatPack, so that they expose the current record
type, but I doubt there is any point waiting for it.  If they did implement it, then you would
not need to have any special record types e.g. "header and "trailer"

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message