Jan 7th, 2012, 02:37 PM
Business Logic with the Active-Record Pattern in Roo?
I've decided to fully remove the services and repositories from my roo project that I'm working on and just do active record as it seems to simplify things to help me get more done faster.
The one thing I'm wondering is what other developers using this pattern do for business logic that would normally go in the service layer? Thus far I have resorted to putting the logic directly into controllers. I don't think most logic I am implementing would be long in a getter / setter on the entity itself.
I have thought of using the controller, where needed, as sort of a replacement for what would have been the service layer, such as I won't directly interact with the database through the active-record object except for within its controller (in order to keep business logic intact and not have to replicate it).
I would be curious to hear other's thoughts on this.
Tags for this Thread