Mediator | A high performance implementation of Mediator pattern in NET using source generators | Dependency Injection library

In the startup constructor, you create a new configuration builder that has a limited set of sources and lacking the Azure Key Vault provider. So instead of creating a new configuration builder perhaps you could inject the one that is readily available in the DI container.

So change the startup constructor with this.

Currently, after the dblookup the query result is your message. So if you respond after the log statement for example but skip the enrich, you should send those variables back to the client.

You could also use a PayloadFactory or XSLT transformation to transform the message if you want. But the data is already there, you actually lose it right now due to the enrich.

Where is CreditCard marked as non-owned?

In JobSeekerContext here

The correct expression should be get-property() [1]. Can you try that.

[1]-https://ei.docs.wso2.com/en/7.0.0/micro-integrator/references/mediators/property-reference/accessing-properties-with-xpath/#get-property-function

You may use JsonDocument.RootElement.GetRawText() to get the original JSON with the original formatting. From the docs:

JsonElement.GetRawText Method

Gets a string that represents the original input data backing this value.

Thus, you may just do:

This is an issue with your container, not MediatR or the DI extensions library. You'll want to register an open generic if you want the variance to kick in. Something like:

Based on the shown code, the subject under test uses AcceptConditionalRiskAgreementCommand

I managed to come up with a working, but likely inefficient and potentially buggy solution. By putting each IAsyncEnumerable into its own background task, I'm able to emit each into a thread-safe queue, where they're served up as each one comes available.

If you want to send, just JSON message as payload to RabbitMQ, don't use message store. Message stores, are storing all synapse message context with payload for later processing - that is their purpose. So that is why you see in decoded RabbitMQ Payload not only the message, but also additional properties.

For sending JSON to RabbitMQ you can use just to a proper endpoint. Look as this documentation sample. I have also have made some sequance template for more easy use of sending messages to rabitmq, so next you can may look at this helpful post, and adapt to your own needs.