Hello everyone, I'm a newbie in DDD, I have read some books, but I'm having many trouble in doing a real world application in DDD. I can see that many people...
For those of you using Specifications to validate, has anyone added a mechanism to report why an object fails to meet a Specification? Here's a contrived...
This is something I've been thinking about too. Currently we use the state pattern, so a Customer has a CustomerState object. When you ask a Customer whether...
There is a lot of discussion about different technics to use in DDD, and many of them have some focus on the aggregation root when peforming stuff. The...
... I'm having ... Take a look at this framework stuff: www.lhotka.net It might get you a head start on practical use of some of the patterns and practices...
... class SpecReturn with properties: boolean satisfied; Cause cause; ... class Cause with properties: String message; //mesage to display int causeType;...
Exceptions are best used for exceptional cases. It sounds to me like this is not really an exceptional case (I might have misunderstood). For a similar problem...
Although in the DDD book there are many concpets about modularizing the domain itself I am often faced with tackling heavy entities. In many domains there is a...
I have this exact same problem but hadn't put words to it. The greedy aggregate is indeed something that feels bad, but is it? I look forward to the comments...
In my experience, it helps to be a little less formal about the concept of an aggregate root. I know that we have had heavy debates on this earlier, for good...
This is really the point of the aggregate pattern. Systems don't work well with those megalithic models. When your model seems to demand a single huge...
I've dealt with what sounds like a similar problem. At a previous job we had an application that performed various types of batch processing on a very large...
interesting. I will have to look at my object model this way and see if that helps. along with eric's advice as well. thanks team!!!! -d ... -- cheers, -d...
Anyone use naming conventions to differentiate between an entity object and a value object? So instead of CUser and CUserStatus I might have eUser vUserStatus...
For me this falls in the same category as naming variables with a datatype prefix (remember hungarian notation?). The problem occcurs when your model evolves,...
I would imagine the class's type would be obvious from your domain language. If it isn't, I would focus your attention back to there. I personally dislike...
This type of naming convention might scare me ... What happens if I refactor an entity to be a value object or vice versa? There is now a type coupling...
This can rapidely fall into a religious debate. But before it does, just to compensate the other side, I would argue that refactoring using a good IDE would...
What purpose does that particular distinction serve? I can't, offhand, think of any reason I'd care to know that about a class, and not a whole lot more. Also,...
Thanks for the quick responses. I personally don't think it is necessary. However, someone in my group recently proposed this idea and I wanted to present any...
Thanks John, that's what I was looking for really. What point does it serve. If none of you are doing it then it almost "proves" my point that we are not going...
... wrote: ... Are you really discussing the specific detail about whether or not one should use naming conventions for entity/value objects or are you not ...
I saw tomtdd's long post but figured I would chime in with my simple approach (as I don't want to get into the debate of why). Originally I was doing something...
Hi Trond-Eirik, Interesting topic. Well, from my point of view I lean far more towards having a repository per aggregate root. One per application will simply ...
I think Patrick's post is where my thinking was going (I will try and confirm if I've got it right). It was the subject of Eric's post that was starting to...
Good discussion. I've had it as well with one of my colleagues, who's a MVP. I have to note up front that I don't know WWF really well, so my opinion is more...
That might be one way to split it, I definitely would try to keep my Customer lightweight but I'm not sure if moving Orders off is the correct way to do that....
I'm not sure I see that being a major problem, replacing the normal state pattern implementation with Activities doesn't seem to me to be that big a jump. To...
