I have some doubts when to use abstract class and if I need to always code interface. An example: I have will have series of custom entities, and all of them need to implement SomeMethod() and most o
In this application I\'m developing, the domain revolves around, say, electrical appliances. There are several specialized versions of this entity. Appliances can be submitted to the application, and
I have a few objects that represent a web application.Currently I have a cluster object to represent a specific deployment of the app.Within a cluster object I have the following objects:Server, Custo
Context: Repository-pattern, WCF, WPF/SL In my Repository of self-tracking Entities i need to explicitly load some related properties in order to correctly process the query. Those are not the include
given the deprecation of loads of design patterns because of the new improvements in the Java EE world, DTO\'s are largely frowned upon.
As I\'m typing this, I\'m realizing that it\'s very hard to explain.My apologies if it\'s indiscernible.My end goal is to have someone with more experience look at how I\'m structuring my solution and
I would like to know the best practice for a class oriented DDD. Since i am doing domain validation in custom setters named ChangeX(string x) i might be pushed to use this as property.
There are several questions on this, and reading them isn\'t helping me. In Eric Evans DDD, he uses the example of address being a value type in certain situations. For a mail order company, the addre
As a non-native English speaker, I often wonder about using the plural form in the initial part(s) of noun phrases when naming classes or objects.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expe开发者_JAVA技巧rtise, but this question will likely so
加载中,请稍侯......