title: nHibernate, an n-Tier solution + request for advice
body: <p>I'm getting the chance to develop a mildly complex project and have been investigating the various approaches that I can use to tackle this project.  Typically I would have ran with the traditional 3-Tier approach but after spending some time looking around at various options I've got an inkling that some kind of ORM might be a better fit and I'm considering nHibernate.  However, I'm looking for some guidance on implementing nHibernate and more specifically how I would structure my BL and DAL in conjunction with nHibernate.</p>
  
  <p>With nHibernate I would create my Objects (or DTOs?) and use nHibernate methods for my CRUD interactions all in my DAL.  But what I can't get my head around is the Objects defined in the DAL would be probably be better situated within the BL, i.e. where validation and other stuff can be performed easily, and I just use the DAL from the various ObjectFactory's / ObjectRepositories.  Unfortunately it seems through the many articles I've read this isn't mentioned or skirted over and I'm a tad confused.  </p>
  
  <p>What is the more accepted or easier method of implementation when using nHibernate in a 3 Tier system?  Alternatively, what is the conventional method of exposing objects through the business layer from the data layer to the presentation?</p>