Allow transactional message handlers. about nimbus HOT 3 CLOSED

Thinking more about this, issue #31 might provide an alternative solution. That could either allow this sort thing to be implemented by the dev user, or offer an alternative way to implement this feature internally.

from nimbus.

Sigh... accidentally closed. Reopening

from nimbus.

I'm closing this because there are too many concerns IRT transactions and service bus, so it's best to not bother with in-built support. Service bus is transaction-aware in that it doesn't allow certain methods to be called in a read-committed (among others) ambient transaction. It seems that while it doesn't support any transaction model, it doesn't like you using one either (I think it's a case of them trying to save us from ourselves).

For those that dig up this tome at a later date due to googling relevant keywords, the way to allow .Send etc to be called from within a suppresed transaction scope. We have a helper for that:

public virtual void NoTransaction(Action action)
{
    using (new TransactionScope(TransactionScopeOption.Suppress, 
               new TransactionOptions { IsolationLevel = System.Transactions.IsolationLevel.Serializable })) 
    {
        action();
    }
}

NoTransaction(() => _bus.Publish(new SomeEvent()))

from nimbus.