[
https://issues.apache.org/activemq/browse/CAMEL-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49125#action_49125
]
Willem Jiang commented on CAMEL-1293:
-------------------------------------
How about set the header for the type ?
Camel already support it out of box :)
The DSL could be
{code}
from("activemq:gold").setHeader("type",
constant("goldCusomer")).to("bean:orderSerivce?method=placeOrder");
{code}
You can use the bean's annotation for the parameter consuming
{code}
public class Foo {
public void doSomething(@Header(name = "type") String type, @Body
String body) {
// process the inbound message here
}
}
{code}
> bean component - ability to pass in additional parameters
> ---------------------------------------------------------
>
> Key: CAMEL-1293
> URL: https://issues.apache.org/activemq/browse/CAMEL-1293
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.5.0
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> Idea from FUSE OS Community
> Invoking a bean and you want to pass in an additional parameter (not from
> Exchange) such as
> Such as
> {code}
> from("activemq:gold").to("bean:orderSerivce?method=placeOrder&type=goldCustomer")
> {code}
> The type parameter is maybe a String type in the placeOrder method that Camel
> should invoke with the text "goldCustomer".
> We can kinda add this with @annotations to bind to the parameter name.
> Maybe we could also support varargs in the java fluent builder with the .bean
> {code}
> from("activemq:gold").beanRef(orderSerivce, "placeOrder", "goldCustomer");
> {code}
> Well I just created the ticket to not forget about it.
> Any thoughts from the other Riders?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
