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
2 months agoZoila
2 months agoMillie
2 months agoGeorgene
3 months agoYoulanda
3 months agoElinore
3 months agoDominga
3 months agoVelda
4 months agoNida
4 months agoAsuncion
4 months agoTamekia
4 months agoTom
4 months agoEvangelina
5 months agoSelene
5 months agoOlga
6 months agoMalinda
7 months agoCary
7 months agoRaymon
6 months ago