Hi Ken, Thanks for the explanation. Yes, that makes sense, and it's an interesting example. My interpretation is that there is an event that occurs in the...
The only reason I keep them in separate packages is because the repositiories have database access (DAO) logic. All my DAO classes are together in a separate...
I always keep repositories and their entities (and any factories) in the same package too. This way the only classes that know about the implementations are...
... package. I'm wary of exposing the DAOs to my service layer. This could allow the service layer to bypass business rules enforced in the repositories. I ...
Hi, i_m new to DDD ... and i wonder if anybody has taken the trouble and created the source code for the example from "Chapter Seven. Using the Language: An ...
Hi Jeff, This is interesting; there have been previous threads where the difference between DAO and Repository has been questioned (as in, is there any). So...
... Repository is that Repository implements some amoutn domain logic, while DAO implements pure data access (assuming some data source)? Almost. The...
My way of viewing it, Repositories belong to the domain. They expose methods that are useful only in the context of the domain and serves for abstraction on...
Hi Randy, I'll explain my example more explicitly. It's a system that, for a given User, aggregates their Bills from multiple RemoteBillers. There's an...
Hi, I have been thinking abt. this for a while that the best place to put a cache for domain objects is the repository. But then, repository is meant for use...
As a rule, I would consider caching as close to your persistence tier as possible - that's where you get most of the re-use. To me, that implies that it's...
Hi, My domain layer is exposed to the UI (there is no DTO). Now the domain has both apis meant to be called from the UI layer (getters and setters for the...
If business rules are constantly changing (let's say every few weeks) how can we manage these changes. It seems as if one strategy is to embed the business...
Let me elaborate this a bit more: The domain layer accesses the repository which in turn invokes the dao layer. The DAO looks up a datasource etc. Now in a...
Hi, My strategy (domain algorithm) classes take in the Domain Entities as part of their (strategy) c'tor. Later on the, when execute is invoked on the...
I would reach for the Strategy pattern first before the Specification Pattern. I'm not sure the Specification would even apply in that situation. You don't...
This issue raises two good questions: When is using a rule engine necessary? How does a rule engine interact with the domain model? In DDD book Eric mentions...
Hi. I have a quick question for the group: Repositories are considered to be part of the domain model, together with entities, value objects and services. I've...
... A domain model is an abstraction; an adaptive object model is a specific implementation technology. An AOM is one way to implement a domain model; it...
Thanks for your time Susan, I caught the terms "Big Bang" and overkill, i wonder did you have a chance to experience AOM and what's the reaction of AOM to add...
That's an interesting viewpoint ("I would not have a domain object reference a repository"). I guess it depends on what is meant by "reference". I recently...
Hi Randy, I kinda agree to your viewpoint. If the entity domain is not supposed to access repository, someone else (Service or Strategy/Policy domain classes)...
Greetings, I'm trying to get a grip on how to use Hibernate (NHibernate actually) in a Repository. Is there a best practice regarding whether to push the...
On Tue, 15 Mar 2005 07:19:34 -0000, Scott Bellware ... In applications I've written repositories are wrappers around the Hibernate APIs. Here is a link to some...
