[CAMEL-11795] service-call : service-call expression should have a way to manipulate headers

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 3.x
• Component/s: camel-core
• Labels: service-call
• Estimated Complexity: Unknown
• Assignee: Luca Burgazzoli
• Reporter: Luca Burgazzoli
• Created: 20/Sep/17 12:48
• Updated: 02/Sep/22 10:55
• Resolved: 02/Sep/22 10:55

Description

From apache-camel:

<lburgazzoli> davsclaus, I'm looking at CAMEL-11711 (Camel-example-spring-cloud-servicecall doesn't work out of the box)
<lburgazzoli> the issue is that
<lburgazzoli> there are some headers like CamelHttpPath now
<lburgazzoli> so i.e. undertow builds the effective url to incoke combining the http uri you give it with info from the headers
<lburgazzoli> so the final call is not more like http://localhost:9012 but it is http://localhost:9012/camel/serviceCall/service1
<lburgazzoli> which does not exists
<lburgazzoli> see this gist https://gist.github.com/lburgazzoli/1a44497db3cb29d2370ee2d125bb741c
<davsclaus> ah yeah you need to remove the CamelHttp* headers
<davsclaus> i guess maybe camel-undertow has been "fixed" since that example was created
<davsclaus> if you use something else like jetty it may have had that "problem" from the beginning
<davsclaus> i guess maybe service call eip should disregard those headers or something? unless you use those expression stuff etc
<davsclaus> where the expression evaluated the url of the service etc

{camel}

Issue Links

• relates to: CAMEL-18453 camel-core - Deprecate ServiceCall EIP