[
https://issues.apache.org/jira/browse/CAMEL-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065096#comment-13065096
]
Claus Ibsen commented on CAMEL-4226:
------------------------------------
Ben you may be able to experiment with ToDefinition to add *optional* support
for an ExpressionDefinition. But its just not easy with JAXB.
If a workaround can be found, we could consider adding it in a future Camel
release. It must be optional to avoid breaking a ton of existing apps / tooling
etc.
> add Expressions support on to(), bean() and beanRef() to allow for dynamic
> endpints (similar to recipientList)
> --------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4226
> URL: https://issues.apache.org/jira/browse/CAMEL-4226
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Ben O'Day
> Assignee: Ben O'Day
> Priority: Minor
> Fix For: 2.9.0
>
>
> just a thought, but any reason we couldn't overload these APIs to also
> support Expressions? Is there another way to do this?
> to(simple("bean:myBean?method=${headers.operationName}"))
> bean(MyBean.class, simple("${headers.operationName}"))
> beanRef("myBean", simple("${headers.operationName}"))
> The goal being to make it (slighlty) easier/more flexible than using
> recipientList for the same...
> recipientList(simple("bean:myBean?method=${headers.operationName}"))
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
