HTTP Header are redundantly mapped to SY Context Properties with Scope MESSAGE and EXCHANGE

Solution Unverified - Updated -

Issue

We use HTTP header to transport governance metadata.

When the headers are mapped into SwitchYard they are persisted into context properties with scope MESSAGE and EXCHANGE. This is inconsistent to the documentation on https://docs.jboss.org/author/display/SWITCHYARD/Message+Composition. We would expect the header only to be present in the MESSAGE scope.

Furthermore when these properties are then remapped into the HTTP message we get inconsistent behaviour. Sometimes the values are read from the MESSAGE scope and sometimes from the EXCHANGE scope.

Environment

  • Red Hat JBoss Fuse
    • 6.3.0

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