[
https://issues.apache.org/jira/browse/CAMEL-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190023#comment-17190023
]
Ganesh commented on CAMEL-15496:
--------------------------------
{{The following method can invoke a bean when the value contains "#bean:" or
"#"}}
{{org.apache.camel.support.EndpointHelper#resolveReferenceParameter(org.apache.camel.CamelContext,
java.lang.String, java.lang.Class<T>, boolean)}}
For my use-case I want to invoke a method in the bean.. Should this have also
support for invoking the method ?
Let's say with the syntax "#bean:<beanRef>?method=<methodName>"
The above is supported in the Camel Route.. Is there any specific reason why it
is not supported in the value ?
> Add support to add additional headers and properties
> ----------------------------------------------------
>
> Key: CAMEL-15496
> URL: https://issues.apache.org/jira/browse/CAMEL-15496
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-rabbitmq
> Affects Versions: 3.4.3
> Reporter: Ganesh
> Priority: Major
> Fix For: 3.6.0
>
>
> See this question
> [https://github.com/apache/camel-kafka-connector/issues/323]
>
> The camel-rabbitmq-sink-connector needs to have support to add additional
> headers.
> While doing so, the basic AMQP properties were also couldn't be added.
> The source kafka connector could be from any source. The headers and
> properties related to AMQP message cannot/should not be added at the source
> level. So, it should always be possible to add and manipulate the headers and
> properties via configuration.
>
> There should be a support to add these headers and properties in the camel
> sink connectors via configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
