Ok guys :-) I am going to ask the dojo group if they don't mind sharing our code. This is a banking Java appliction implementing simple risk analysis ...
... Yes, it is just what I mean when saying to implement Repositories with Separated Interfaces. However, there may be IMHO the need of an object adapter...
... Sample code is all about naive code, keeps it short enough to grok when trying to make a point, and my point was the way in which the templates were used,...
... How about testing? The DAO in your Repository can simply be an interface, with the actual implementation variable in order to allow mocking of the data...
Dave, My comment applies to the case where the repository is a simple pass through and so there would not be any behavior in the repository to test. Of course,...
I've been following the discussion with much detail because when I started learning about DDD I was puzzled about why do people prefer to implement ...
You can have a reasonable compromise by having "wrapper" objects in the domain layer as well as the interfaces. These wrapper objects merely implement the...
The main reason for using interfaces for repositories is to provide room for multiple repository implementations. The first implementation would be one which...
I've used in the past this approach (wrappers). Since the wrappers are not simple interfaces I could use them to do thing like validate entities in a generic...
... I used to have fake implementations of repository interfaces for testing but I found that it was easier to use mock objects provided by jMock or EasyMock. ...
In my mind it is not just about using the first repositories for mocking. By originally using true in memory collections you can design and develop your entire...
On 5/2/06, Alasdair Gilmour <alasdairg@...> wrote: You can have a reasonable compromise by having "wrapper" objects in the ... This is what I mean when...
On 5/3/06, gregory young <gregoryyoung1@...> wrote: In my mind it is not just about using the first repositories for mocking. ... + 1 for Gregory. Using...
... between Repositories and DAOs. ... That is the trade-off. All is not lost, however: it is fairly easy to automate generation of this adapter code - if you...
I've used these kind of wrappers in the past, but I've gotten away from them. It seems easier just to provide different implementations of the repository...
I agree that an in-memory repository is much more than a mock. We've used them for testing, yes. We use them to provide an experimental platform so we can...
I always love that post and direct people to it all the time. When I start building a system I'll always build a repository (when needed) and model it as an...
There is one thing that scares me a bit when building without having a thought about persistence: performance. I discovered that developers get used to the...
... I'd rather them not know, and write all that sub optimal code, it's likely far cleaner and nicer code than they'd have written without it. They can't all...
Hi guys, I'm working on an open source project which will include the implementation of a composite specification. I've talked about it in my blog : ...
Hi Sergio, What are you thinking about error treatment? I mean... How would the client be notified if an specification is not satisfied? Regards, Carlos. PS:...
On 5/4/06, Carlos Miranda <cevmiranda@...> wrote: How would the client be notified if an specification is not satisfied? ... Hi Carlos, I've written a...
John Roth hit the nail on the head that this problem of extensive traversals should be addressed with aggregates. The primary motivation for aggregates is...
Though out this (and another discussion which was occurring in regard to active record vs repository) I tried to flesh out some of the ideas presented ...
I agree with you. A Repository acts as a separation between the domain and the persistence layer. No matter what similarities can be found between the domain...
Hmm. I guess the real point I was trying to make, perhaps I didn't make it very well, was that since the repository translates the differring models it ...
On 5/5/06, aabelro <life.for.all@...> wrote: I can see a case when one would use ActiveRecord, if he had just a few ... Another big problem with Active...
More posts on repositories (like we don't have enough of them). I'm looking at my repositories and they follow a pattern something like this: public class...