[Fuse Online] Path resolution in REST API call fails to append a portion of the relative URL

Solution Verified - Updated -

Issue

Using Fuse Online an integration is deployed that needs to call an external REST service based on an OpenAPI 2.0 (Swagger) definition.

When trying to resolve the URL path from the given OpenAPI 2.0 document the trailing part of the path after the last path parameter place holder is lost.

For example for a REST endpoint URL with path:
http://myrestendpoint:8080/path/{param}/will/be/lost

it gets resolved as:
http://myrestendpoint:8080/path/{param}

and the trailing URL path /will/be/lost is lost.

As a result the API call fails with an error similar to
org.apache.camel.http.common.HttpOperationFailedException:
HTTP operation failed invoking http://myrestendpoint:8080/path/<resolved-param> with statusCode: 500

Environment

  • Red Hat Fuse 7.2
  • Fuse Online
  • OpenShift
  • OpenAPI based REST endpoint definition

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content