"If not, you might be better off ditching EJB, running everything in the in the servlet container (but still rigorously separating into ui and domain logical...
C A L L F O R P A P E R S ============================= The 5th OOPSLA Workshop on Domain-Specific Modeling October 17, 2005 San Diego, California, USA ...
Below is my question and Eric Evans' answer regarding whether you should have a repository reference inside an entity. I hope the answer is helpful to other...
In the applications that I have worked the majority of entities do not need to have access to the repositories. But in a small number of cases it made sense...
Chris, Thanks for your reply. The pros and cons of the three options you described are discussed at great length in the Spring Framework posting I listed below...
I must admit I’m confused with Eric’s reply. I was in the belief that Repositories are a domain concept and thus could be used from the domain the same way...
But then this means holding a reference to the repository, and that's not good, even if you could get your persistence framework to do it. In your scenario,...
... that's not ... FYI, Well, I just did some more research this morning and the Spring Framework has experimental support for injecting dependencies (like ...
... And the reason it is not good is because...? ... I'm not sure why passing in a restaurant instead of the RestaurantRepository would help. The application...
I’ve found that in most cases where I wanted to have an entity call a repository that I could solve it by having the entity raise an event, which would be...
Actually, .NET does have spring: http://www.springframework.net It's not as far along as the java version, obviously, but it's still pretty functional. -...
Griffin Caprio
griffincaprio@...
Jun 6, 2005 8:22 pm
2315
Is calling a Repository from a Specification ok, and are specifications at the same level as Repositories? If so can why can I use specifications form entities...
... I believe it is perfectly OK to have Specifications to be associated with Entities. The are (Specifications) domain concepts, after all. I'll give a small...
Actually I’m not even sure I’m using them correctly, hence my questions. Since I started the project I believe I could have done the validation with ...
I make a clear distinction between a Repository and a DAO. A Repository is a model elements that exposes a public interface for working with a Context Root,...
... In my mind, DAO and Repository are synonymous. This became clear to me when I studied the TradeOrderRepository collaboration diagram in figure 6.21 on page...
On page 155 it says "The REPOSITORY will delegate to the apropriate infrastructure services to get the job done". The DAOs are the infrastructure services. ...
... I interpreted "infrastructure services" to mean something like Spring-JDBC, raw JDBC, Ibatis SQL maps or Hibernate (in which case the SQL passed is...
... implementation of _TradeOrderRepository_ that doesn't need a database (e.g. contains a Map of trackingIDs and TradeOrders). As long as it returns an...
... Okay. I think I see where you are coming from too. :-) ... As an aside, I just want to mention that I recently started making interfaces for just about...
Yes, that is step 2 in Rod's "recipe" for TDD (step 1 is defining the interface). Anyway, I really recommend that any enterprise Java developer read Rod's...
I believe that Repositories live ini the "lower" part of the domain layer, i.e. near boundary of the domain and persistence layers. And I believe it is...
Hi all, Yes, my internal visualization is of free floating domain object collaborating in networks and making use of Repository resources, visually below or...
Lately I've been playing with Smalltalk a lot, and have taken to the habit of having a classes repository as a class instance variable so I can find any...
Ah, Smalltalk. Thanks, Ramon. That's a good use of (meta)class instance variables and a good example of something that can only be crudely simulated, at...
Currently, the repository is specific to the type of object it contains, to allow a place to put specialized query methods, but it gets most of it's behavior...