Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 4 Jan 2017 20:11:58 +0000 (UTC)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12546513.1331772338000.642270.1483560718361@Atlassian.JIRA>
In-Reply-To: <JIRA.12546513.1331772338000@Atlassian.JIRA>
References: <JIRA.12546513.1331772338000@Atlassian.JIRA> <JIRA.12546513.1331772338827@arcas>
Subject: [jira] [Commented] (CSV-66) Bean mapping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 Jan 2017 20:12:00 -0000


    [ https://issues.apache.org/jira/browse/CSV-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799205#comment-15799205 ] 

Gary Gregory commented on CSV-66:
---------------------------------

I am not convinced this is in scope for CSV but I am curious.

I'd like to see a design proposal before someone spends a ton of time on a patch.

Should this be in CSV or in an add-on module?

If within CSV, it should be in a cleanly separated package.

Would it make sense to reuse annotations from JPA or elsewhere or would this be too confusing?

> Bean mapping
> ------------
>
>                 Key: CSV-66
>                 URL: https://issues.apache.org/jira/browse/CSV-66
>             Project: Commons CSV
>          Issue Type: New Feature
>          Components: Parser, Printer
>            Reporter: Emmanuel Bourg
>             Fix For: Patch Needed, 1.x
>
>
> Commons CSV needs a way to easily read/write a collection of beans from/to a CSV file. Annotations could be used to map precisely the object fields to the CSV columns.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)