NHibernate persistence supports a mechanism that allows using the same data context used by NServiceBus internals to also store business data. This ensures atomicity of changes done across multiple handlers and sagas involved in processing of the same message. See accessing data to learn more about other ways of accessing the data in the handlers.
The NHibernateStorageContext can be used directly to access NHibernate ISession.
If different connections strings were used for particular persistence features, such as sagas and timeouts, then
context.SynchronizedStorageSession.Session() will expose connection string for sagas.Using in a handler
public class OrderHandler :
IHandleMessages<OrderMessage>
{
public Task Handle(OrderMessage message, IMessageHandlerContext context)
{
var nhibernateSession = context.SynchronizedStorageSession.Session();
nhibernateSession.Save(new Order());
return Task.CompletedTask;
}
}
Using in a saga
Other than interacting with its own internal state, a saga should not access a database, call out to web services, or access other resources. See Accessing databases and other resources from a saga.
If the situation is special enough to warrant going against this recommendation, the following documentation will describe how to do so.
public class OrderSaga :
Saga<OrderSaga.SagaData>,
IHandleMessages<OrderMessage>
{
public Task Handle(OrderMessage message, IMessageHandlerContext context)
{
var nhibernateSession = context.SynchronizedStorageSession.Session();
nhibernateSession.Save(new Order());
return Task.CompletedTask;
}
Regardless of how the ISession object is accessed, it is fully managed by NServiceBus according to the best practices defined by NServiceBus documentation with regards to transactions.