same here, with a different reason though. IRepository is a domain term, and as such should be ignorant of NH, specifically DetachedCriteria.
so my IRepo.Find will accept an IFilter, and on the implementation layer I'd translate that into a DC (or namedQuery is the filter is simple enough), and forward to call either to the ISession directly, or to rhino's IRepo On Wed, Nov 12, 2008 at 6:26 PM, Gabriel Schenker <[EMAIL PROTECTED]>wrote: > In my projects I never have used IRepository<T> of Rhino Commons. I've > always defined my own IRepositoryBase<T> (with much less methods) and have > only used Repository<T> of Rhino Common in my repository implementations... > I am a believer in simple interfaces. > > > On Wed, Nov 12, 2008 at 5:13 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > >> For a long time, IRepository<T> has been bothering me.In particular, we >> have literally scores of methods there, and the interface is way too big and >> complex. >> >> My current action is to move the IRepository<T> and associates to their >> own project, thoughts? >> >> >> > > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
