Hi all.

In NHibernate in Action, last chapter, the authors present the
GenericDAO<T, ID> pattern.

It looks very clean to me.

When approaching to write a brand new architecture for a non-trivial
information system, would you systematically use this pattern for all
the involved persistent classes? Are there some disadvantages in doing
so?

Can this pattern hide NHibernate machinery behind the persistency
layers thus avoiding to completely exploit its functionalities (e.g.
ToFuture())?

Thanks in advance,
marcello esposito.

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to