Outgoing messages are not persisted in the transactional outbox

[salvobellino95]

After #2299 was fixed, cascading messages generated by handlers decorated with [AlwaysPublishResponse] publish the messages, but without using the transactional outbox, if configured.

I attached a sample project to reproduce the issue. In the example, CreateTodoItems handler will publish the cascading message TodoItemsCreated without using the outbox

WolverineExample_Issue2.zip

[dmytro-pryvedeniuk]

@jeremydmiller I also see Inline mode generated by dotnet run -- preview for Handler project and looks like it's not only preview.
The message is not durable despite of using opts.Policies.UseDurableOutboxOnAllSendingEndpoints(); We can see it in debug.

As a workaround I used .UseConventionalRouting(x => x.ConfigureSending((ex, _) => ex.UseDurableOutbox())); Preview shows that it makes it durable. See the difference in debug.

To make reproduction easier attaching docker-compose (to run db and rabbit) and .http file (to trigger the request).
extra.zip

[jeremydmiller]

@dmytro-pryvedeniuk @salvobellino95 I think it's also quite possible that we have a bug in the dotnet run describe output. That has been an issue before with the combination of conventional routing + endpoint policies