[
https://issues.apache.org/jira/browse/CAMEL-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909236#comment-17909236
]
Claus Ibsen commented on CAMEL-12953:
-------------------------------------
Actually I cant easily see how those headers would map to the grpc stub. What
parameters should headers be mapped to, and how
> Camel grpc component doesn't transfer the Message headers
> ---------------------------------------------------------
>
> Key: CAMEL-12953
> URL: https://issues.apache.org/jira/browse/CAMEL-12953
> Project: Camel
> Issue Type: New Feature
> Components: camel-grpc
> Affects Versions: 2.22.1
> Reporter: Vishal Vijayan
> Priority: Minor
> Labels: help-wanted
> Fix For: Future
>
>
> Headers that are added to the Message in the camel Exchange before making a
> call to the camel-grpc component are not received at the grpc consumer. The
> expectation is that these headers would be added to the grpcStub before
> sending over the wire (like other components like http4 etc).
> Our team has come up with a workaround for this but it is extremely
> cumbersome. We had to extend the GrpcProducer to introduce a custom
> GrpcExchangeForwarder that would copy header from exchange to the stub before
> invoking the sync/async method.
> At the consumer side we had to extend the GrpcConsumer to use a custom
> ServerInterceptor to capture the grpc headers and custom MethodHandler to
> transfer the grpc headers to the Camel exchange headers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
