camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: unmarshall csv problem with bindy
Date Sun, 06 Jan 2013 10:30:28 GMT

Yeah I think bindy has some issues with parsing data that has optional quotes.

We recently fixed an issue and improved the quote parsing. But there
was an incompatible change so it was only applied on trunk, eg Camel

I suggest if you got a bit of time, to try your code against Camel
trunk and see if that fixed your use-case as well.
If not, then feel free to log a JIRA ticket. So we can get it fixed in 2.11.

On Thu, Jan 3, 2013 at 4:14 AM, Ramiro <> wrote:
> Im working with Karaf 2.2.10 and Camel 2.10.1. I receive a file, parse the
> csv to a pojo, and do some other suff. My problem is that if a field in a
> record on the csv ends with a coma like the third field here:
> someFieldValue,someOtherFieldValue,"aaaa ,",moreStuff
> It puts together aaaa , with moreStuff in a single field(ignoring the
> second quote). But if i add something like:
> someFieldValue,someOtherFieldValue,"aaaa , bbb",moreStuff
> It gets processed without a problem(aaaa , bbb in a field, moreStuff in
> another). Seems like Camel is interpreting the ," pair like something to
> escape.
> Im using comma as the separator, and i've tried with other separators and
> setting the quote attribute of the @CsvRecord to single and double quotes.
> Is this expected behaviour, or some known bug? Any workarounds?

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message