When I upgraded the http client version of camel-http4 to 4.3.x, there were some API changes in http client just like common-csv. As we can do some adaption inside camel-http4, I just changed the configuration a bit. I think we can do the same thing in camel-csv :)
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On September 10, 2014 at 10:57:03 PM, Claus Ibsen ([email protected]) wrote: > Hi > > Welcome back. > > I suspect the breakings is less affected by Camel users, eg I would > assume the data it creates on the Camel Exchange / Message / body / > headers can be the same as before? So the changes affected is maybe > how to configure it using the csv data format or its csv config > object? > > I am fine to make this change for Camel 2.15 and add some notes to the > release notes that end users need to do some changes. > > > > On Wed, Sep 10, 2014 at 4:46 PM, Antoine DESSAIGNE > 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 :) > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ >
