Not really. I can choose.
One more thing. The DAO abstraction spring provides, and how it is commonly put to use with a data mapper (especially Hibernate). Too me it actually sounds exactly what Evans describes as a Repository. A object that is responsible for reconstructing and persisting entities. I'm just courious.
That reminds me, I didn't reacted to the discussion UserManager vs UserRepository/Registry.
No it would not change. If the functionality would be the same. But it UserManager would execute business specific logic (like calculating shipping or the like) and UserRepository would not, i'd not go so far calling UserRepository a business service.
And what is business logic by the way? The only definition I found was a german one: "Im oo-Designkontext als Programmteil zu verstehen, welcher die durch die Use Cases ergebende Logik und die zugehörige Architektur definiert ist." http://www.hta-bi.bfh.ch/Projects/vs...html/g780.html
The definition says nothing more than every logic which results of a use-case and which defines the appropriate architecture is considered business logic. But this definition is highly questionable. What is a use-case in this context? What is architecture here? I use 'business logic is all logic directly required by a business process'... .
So does anyone have reliable definitions for business service, business logic, business object etc.? I don't like to fuzz with these words.