[
https://issues.apache.org/jira/browse/CAMEL-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264917#comment-13264917
]
Claus Ibsen commented on CAMEL-3496:
------------------------------------
Also if you use a type class, and there is only 1 pojo, then the pojo is not
wrapped in a list. This makes it easier for 1:1 mappings.
> camel-bindy - Make it easier to use by getting rid of List<Map> structure and
> other improvemets
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-3496
> URL: https://issues.apache.org/jira/browse/CAMEL-3496
> Project: Camel
> Issue Type: Improvement
> Components: camel-bindy
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 3.0.0
>
>
> 1)
> The bindy API is unfortunately a bit cumbersome because it stores its result
> in a {{List<Map<String, Object>>}} structure.
> Instead it should store the object directly in the {{List<Object>}}
> End users would expect this instead of the cumbersome API.
> 2)
> Also the marshal and unmarshal operators should take an optional class name
> so you know which class to use in case you use a package which has other
> @CsvRecord classes in the same package. Then you can tell Camel to use this
> class in case of ambiguity.
> 3)
> And if you use multiple objects for one @Record we should introduce an option
> on the @Record to mark the class as the *top* class (the starting class).
> 4)
> And the source code could use a bit of love here and there, and most likely
> add more checks and throw better exceptions so end users better understand
> what would be wrong.
> This will break backwards comp. so let's try to do this for Camel 3.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
