[ https://issues.apache.org/jira/browse/CAMEL-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea resolved CAMEL-6648. ------------------------------------ Resolution: Won't Fix A better approach would be to create a DSL for creating messages specific to the application domain. The low level ProducerTemplate could then stay simple. > 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 > Fix For: Future > > Attachments: CAMEL-6648.zip, FluentProducerTemplate.java, > FluentProducerTemplateTest.java, 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 was sent by Atlassian JIRA (v6.1#6144)