camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9663) CXF Header dropped when multiple CXF endpoint in the same route
Date Fri, 10 Mar 2017 09:28:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904778#comment-15904778
] 

Claus Ibsen commented on CAMEL-9663:
------------------------------------

Do you have an unit test or sample project that reproduces this issue?

> CXF Header dropped when multiple CXF endpoint in the same route
> ---------------------------------------------------------------
>
>                 Key: CAMEL-9663
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9663
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxfrs, camel-test
>    Affects Versions: 2.16.2
>            Reporter: Suresh Kumar
>
> We have multiple cxf endpoint in the same camel route. 
> Following route causes the problem
>   from("cxfrs:server....")
>     .process("prepareHeader")
>     .to("cxfrs:client....")
> When CXF receives a request, It sets the header for a response class which is to be returned
by rsserver. Same response class is passed to rsclient in the camel header. For our usecase
we are substituting the rsclient response class. When rsclient invokes the cxf endpoint we
could see cxf headers in the interceptor but the same headers are not there in camel headers.
> I have debugged the cxf code and found the issue in the following code base
> Class: CxfRsProducer
> Method: invokeHttpClient
> Line number: 222
> invokeHttpClient method invokes cxfendpoint using cxf code base and converts into the
user-defined-class which in turn drops the cxf headers. So CXF headers are not mapped to the
camel header. When we remove the response-class in the camel header then invoke method from
CxfRsProducer:210-line is invoked. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message