Hi Antoine, For sure, if the integration of the new API with the old supported by camel dataformat will request a huge refactoring, this is logic to create a new dataformat for camel-csv2. Alternative is too deprecate what we support now but I don't think that this is a good idea.
Regards, On Wed, Sep 10, 2014 at 4:46 PM, Antoine DESSAIGNE < antoine.dessai...@gmail.com> wrote: > Hi everyone, > > I was looking at this issue : > https://issues.apache.org/jira/browse/CAMEL-7716. > > In fact, the commons-csv library changed a lot between the version that > camel uses and the official one. In addition, there is lot of nice stuff > such as: > * immutable configurations, it's no longer required to copy the > configuration > * build-in iterator mechanism > * etc... > > Supporting the commons-csv API would break the compatibility with existing > code and usage. > > What should I do ? Break compatibility ? Create a new data format ? > > Thanks a lot for your insights on this matter, > > Have a nice day, > > Antoine. > > PS: I was very busy, but now I managed to freed up time for camel :) > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
