[jira] [Assigned] (CAMEL-12953) Camel grpc component doesn't transfer the Message headers
[ https://issues.apache.org/jira/browse/CAMEL-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-12953: -- Assignee: (was: Dmitry Volodin) > 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: Major > Fix For: 3.0.0, 2.24.0 > > > 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 (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12953) Camel grpc component doesn't transfer the Message headers
[ https://issues.apache.org/jira/browse/CAMEL-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-12953: -- Assignee: Dmitry Volodin > 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 >Assignee: Dmitry Volodin >Priority: Major > > 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 (v7.6.3#76005)
