You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2019/12/11 07:10:00 UTC
[jira] [Updated] (CAMEL-14288) Endpoint configurer should deal
better with list types
[ https://issues.apache.org/jira/browse/CAMEL-14288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-14288:
--------------------------------
Description:
When you set list types from a string value in endpoint uri, then it should deal better when we refer to beans in registry, which will be a single entity that should be wrapped into a list.
The bean reflection configurer could handle this, but the new optimized source code generated configurer didnt
was:
When you set list types from a string value in endpoint uri, then it should deal better when we refer to beans in registry, which will be a single entity that should be wrapped into a list. And also for string values separated by comma, that should be a list with the splitted string.
The bean reflection configurer could handle this, but the new optimized source code generated configurer didnt
> Endpoint configurer should deal better with list types
> ------------------------------------------------------
>
> Key: CAMEL-14288
> URL: https://issues.apache.org/jira/browse/CAMEL-14288
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 3.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.1, 3.1.0
>
>
> When you set list types from a string value in endpoint uri, then it should deal better when we refer to beans in registry, which will be a single entity that should be wrapped into a list.
> The bean reflection configurer could handle this, but the new optimized source code generated configurer didnt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)