Who said you that "NHibernate is written to map to classes" don't know NH ?Not only you can map interfaces but you can even persist interfaces without a real implementation of each entity class.
This is my first blog post (before it I was "only" a coder ;) ): http://fabiomaulo.blogspot.com/2008/10/less-than-few-is-gof.html After read that take a look to the second post. http://fabiomaulo.blogspot.com/2008/10/less-than-gof-is-hbm.html or this http://fabiomaulo.blogspot.com/2008/10/entity-name-in-action-entity.html “Program to an interface and not to an implementation” is a "must" in NH. Don't be heretic! LOL 2009/4/30 everettmuniz <[email protected]> > > How do those of you with experience in DDD structure your factories/ > repositories? Do you have them work against interfaces or classes > (abstract or otherwise)? > > I've coded most of the core domain logic in my current project w/o a > lot of consideration for the persistence mechanism knowing in the back > of my mind that I would be hooking NHibernate in after the fact. In > the last few days I've been doing just that and it's been relatively > straight forward. Currently, the domain and the services are written > against interfaces but given NHibernate is written to map to classes > I'm wondering if it wouldn't make more sense to adjust the factories > and repositories to work with the concrete implementations of domain > entities/value-types. > > How have you all addressed this in your projects? > > > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
