Im thinking about using NHIbernate, what affect will it have on my design/implementation decisions?
You do not have to subclass any kind of persistent base class to make objects persistable. You do not have to decorate all your classes with attributes. You do not have to provide any parameterised constructor in your business objects so that NH can create them You do have to provide an default (empty) constructor, with any visibility (public, private etc) You do have to provide property get/sets for all persisted fields, with any visibility you like …Apparently, these last 2 limitations are set to change I think. It must be possible in .NET, as the DADO mapper works this way. Personally, I think they’re a small price to pay anyway. I can unit test how my business objects behave without even having to hit the database, simply by not using NHIbernate in those tests ( I have other tests to prove that my mapping files are set up ok)… You do have to create an XML file that defines how things work. …but this is really easy. AND, there are tools around to help you auto-generate your XM
Related Questions
- How will the implementation of Live Gamer affect developments decisions on Bound on Equip and Bound on Pick-up itemization in future content?
- What types of design decisions will be affected by implementation of the Strategic Highway Corridors concept?
- Who makes the decisions regarding design and implementation?
