[
https://issues.apache.org/jira/browse/CAMEL-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749950#comment-13749950
]
Raul Kripalani commented on CAMEL-6648:
---------------------------------------
[~jhm] – perfect! Give it a go and let me know if you need help. I'll try to
check into #camel these days.
In terms of the asyncStyle/request/send/inOut/etc. methods, in my head there
are only two actions: request and send, whereas asyncStyle is a "modifier" or
switch.
However, at this point I also agree with you both, [~davsclaus] & [~jhm], we
should keep it as simple and familiar as possible in this first implementation.
So let's use asyncSend, send and request for the method names that trigger the
dispatch.
Regarding Futures, they are useful when doing complex routing from within a
bean inside a Camel route, so I'd like to see them in the 1st implementation.
Also, it would be useful to extend the @EndpointInject annotation so that it
injects a FluentProducerTemplate if the variable is defined with such a type.
> Create a Fluent ProducerTemplate
> --------------------------------
>
> Key: CAMEL-6648
> URL: https://issues.apache.org/jira/browse/CAMEL-6648
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Attachments: ProducerTemplateBuilder.java,
> ProducerTemplateBuilderTest.java
>
>
> Create a Fluent ProducerTemplate so that users can use it in the following
> manner:
> \\
> \\
> {code}
> // initialize ProducerTemplate with a default endpoint
> FluentProducerTemplate template = new
> FluentProducerTemplate("activemq:queue:foo");
> MyResponse response =
> template.newExchange().toDefaultEndpoint()
> .withBody("this is slick")
> .withHeader("MyHeader1", "HeaderValue")
> .withHeader("MyHeader2", "HeaderValue2")
> .resultAs(MyResponse.class)
> .dispatchInOut(); // or inOnly(), asyncInOut()
> {code}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
