-
1. Re: cxf-bc and http headers
allanon76 Jan 27, 2011 6:58 AM (in response to kevin.sailly)Hi,
I've the same problem using
from( jetty:host?bridgeEndpoint=true ).to (externalhost?bridgeEndpoint=true)
when passing from jetty:http to external host the header is lost.
Michele
-
2. Re: cxf-bc and http headers
davsclaus Jan 27, 2011 7:02 AM (in response to allanon76)What version of Camel are you using? And what header is lost? Provide an example.
-
3. Re: cxf-bc and http headers
allanon76 Jan 27, 2011 9:00 AM (in response to davsclaus)Hi,
I'm using apache-servicemix-4.3.0-fuse-03-00.
So the camel version should be the one integrated with the ESB.
In general the problem I see is that for example
the Content-Type attribute in the http header is lost.
This cause an error in the remote service.
(statusCode: 415).
12:20:01,495 | ERROR | tp33395264-39590 | DefaultErrorHandler | rg.apache.camel.processor.Logger 248 | 72 - org.apache.camel.camel-core - 2.4.0.fuse-02-00 | Failed delivery for exchangeId: 80985aa8-ff2a-43b4-80dc-b76a6acd1edb. Exhausted after delivery attempt: 1 caught: org.apache.camel.component.http.HttpOperationFailedException: HTTP operation failed invoking http://host:8080/OpenScout_Competence_Webservices/CompetenceServicesService with statusCode: 415
org.apache.camel.component.http.HttpOperationFailedException: HTTP operation failed invoking http://host:8080/OpenScout_Competence_Webservices/CompetenceServicesService with statusCode: 415
at org.apache.camel.component.http.HttpProducer.populateHttpOperationFailedException(HttpProducer.java:157)[183:org.apache.camel.camel-http:2.4.0.fuse-02-00]
at org.apache.camel.component.http.HttpProducer.process(HttpProducer.java:99)[183:org.apache.camel.camel-http:2.4.0.fuse-02-00]
For now what I've done is to add manualy the Content-Type using a processor before calling the external service
from(jetty:http://blabla).process(addHeader).to(external endpoint).
Edited by: allanon76 on Jan 27, 2011 2:00 PM
-
4. Re: cxf-bc and http headers
davsclaus Jan 27, 2011 9:59 AM (in response to allanon76)Thanks for the details.
I have created a ticket to track this