[ https://issues.apache.org/jira/browse/CAMEL-12428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458484#comment-16458484 ]
Daniel Kulp commented on CAMEL-12428: ------------------------------------- Yes and no.... ContentType and response code work as I specially handle them, but general generic setHeader("foo", "blah") will not work. I'm not sure what to do about that yet. > Cannot use Camel exchange headers in Processor with cxf-rs > ---------------------------------------------------------- > > Key: CAMEL-12428 > URL: https://issues.apache.org/jira/browse/CAMEL-12428 > Project: Camel > Issue Type: Bug > Components: camel-cxfrs > Affects Versions: 2.21.0 > Reporter: Daniel Kulp > Assignee: Daniel Kulp > Priority: Major > Fix For: 2.21.1 > > > If you do a simple route from a "cxfrs:" endpoint into a processor that does > standard "camel" type things like: > {code} > exchange.getOut().setBody("Can't found the customer with uri " + path); > exchange.getOut().setHeader(Exchange.CONTENT_TYPE, "text/plain"); > exchange.getOut().setHeader(Exchange.HTTP_RESPONSE_CODE, "404"); > exchange.getOut().setFault(true); > {code} > the setHeader values are ignored and not sent back to the client. They > always get response code 200. If you use a javax.ws.rs.core.Response > object, it works fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)