When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?
When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID. Reference: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes
Stephaine
8 months agoZoila
9 months agoMillie
9 months agoGeorgene
9 months agoYoulanda
9 months agoElinore
10 months agoDominga
10 months agoVelda
10 months agoNida
10 months agoAsuncion
10 months agoTamekia
11 months agoTom
11 months agoEvangelina
11 months agoSelene
11 months agoOlga
1 year agoMalinda
1 year agoCary
1 year agoRaymon
1 year ago