Contents
Why is a repository pattern important?
The Repository pattern makes it easier to test your application logic. The Repository pattern allows you to easily test your application with unit tests. Remember that unit tests only test your code, not infrastructure, so the repository abstractions make it easier to achieve that goal.
Why do we use repository pattern in MVC?
The repository pattern is intended to create an abstraction layer between the data access layer and the business logic layer of an application. MVC controllers interact with repositories to load and persist an application business model.
How are NHibernate objects passed to the repository?
In this case, the Person class is a strict DTO data transfer object and contains no data access methods. All NHibernate types in this scenario would be passed to the repository to execute NHibernate database methods. The NHibernate business object model provides methods on each NHibernate type for saving and loading in the database.
Is it optional to use NHibernate transaction pattern?
The above code is using an NHibernate transaction via the repository pattern, but using a transaction is optional. You could leave out the transaction commands, in which case NHibernate’s standard session will be used.
Is the repository pattern optional in ASP.NET?
As you can tell, the repository pattern really speeds up the integration of NHibernate’s methods with our C# ASP .NET web applications. The above code is using an NHibernate transaction via the repository pattern, but using a transaction is optional.
How are DTO types passed into the NHibernate class?
NHibernate DTO types will be passed into this class for data storage or retrieval. We implement the class, based upon the repository interface, as follows: The first item to note is that the repository implements our IRepository interface, which provides the basic Save, Load, Delete, List methods.