NHibernate has Unit of Work built in.

In the Agatha's case study, why do you insist on providing a UnitOfWork interface and a NHUnitofWork implementation class? You do not use it, after all!!!

I think, it was a copy and paste from Chapter 7, where you presented a sample UoW implementation using Dictionaries.

But, in the case study, where NHibernate is used, you never need it in your code:

- You never use the repository interface passed as parameter in the NHUnitOfWork class methods (Chapter 11, page 462).

- You pass the UoW as a parameter to the Repository but you never actually use it in the methods! (Chapter 11, page 463,464).

Instead, you always let the NHibernate session do the job, which of course is correct (since Session handles all the UoW implementation, itself):

SessionFactory.GetCurrentSession().XYZ


So, please, fix the sample code and the download files for the case study.

Thank you.

Hi dpant,

In my new book (http://www.amazon.com/Professional-D...dp/1118714709/) I look present a slightly better way to use repository pattern and unit of work with NHibernate. The book is not out yet but you can get the source code here https://github.com/elbandit/PPPDDDCh...bernateExample.

Hope this helps
Scott

Thank you for your reply.

Yes, I see you pass the ISession as a parameter to the repository considering it as the unit of work. Now, this makes sense.

As far as application structure is concerned , I truly hope your new book is much simpler than this one.

Thank you again, for replying.