Well you wouldn't necessarily have to make a repo for every entity because you'd have a generic Repo<T> you could use. However you might create (as an example) a UserRepo : BaseRepo<User> with a FindByUsername method as a little syntactic sugar.
I think many people would use a container such as windsor to avoid having to manually instantiate their repositories. On Mon, Jan 26, 2009 at 11:02 AM, Mark Jensen <don...@gmail.com> wrote: > > Hi > > From what i can read on the internet people do really like this > combination due to the placement of the persitance logic. > > how ever, i know that Castles AR has something callsed > ActiveRecordMediator which seems to be the solution to the problem > above. (i also know ayendes rhino commons which also have an > implementation of the repository pattern). > > The questions are. > > 1. Will i lose something if i stop inheritting from ActiveRecordBase > and use ActiveRecordMediatior instead? (to me it seems like i will get > a lot more functionality/control) > > 2. Can someone me how to implement the Repository pattern with > ActiveRecordMediator. I have found this example here > > http://www.lostechies.com/blogs/johnteague/archive/2008/05/27/using-database-repository-pattern-with-activerecord-with-activerecordmediator.aspx > > but to me it seems like I would have to make a Repository (and inherit > from BaseRepository) for every Aggregate and then I need to > instantiate the Repository it when i want to use it. > > Is there a better way of doing this? > > > :) > > best regards, > Mark > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
