camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Ribeaud (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-10840) CsvDataFormat.setRecordConverterRef not usable
Date Thu, 16 Feb 2017 07:48:41 GMT
Christian Ribeaud created CAMEL-10840:
-----------------------------------------

             Summary: CsvDataFormat.setRecordConverterRef not usable
                 Key: CAMEL-10840
                 URL: https://issues.apache.org/jira/browse/CAMEL-10840
             Project: Camel
          Issue Type: Improvement
          Components: camel-csv
    Affects Versions: 2.18.1
            Reporter: Christian Ribeaud
            Priority: Minor


Following interface {{org.apache.camel.dataformat.csv.CsvRecordConverter}} is *package* protected.
This is actually fine because it is used internally. There are two implementations in {{CsvRecordConverters}}.
However {{org.apache.camel.model.dataformat.CsvDataFormat}} contains following *public* methods:
{code:java}
public String getRecordConverterRef() {
    return recordConverterRef;
}

/**
 * Refers to a custom <tt>CsvRecordConverter</tt> to lookup from the registry
to use.
 */
public void setRecordConverterRef(String recordConverterRef) {
    this.recordConverterRef = recordConverterRef;
}
{code}
So, it seems possible to specify my own {{CsvRecordConverter}} but, because of the point mentioned
earlier, this is actually NOT (easily) possible.
I came across this point because I was looking for a mechanism allowing me to proxy the values
being taken from {{CSVRecord}} to *Map* or *List*.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message