I have a root object that has a property that is a collection. For example: I have a Shelf object that has Books.
I have a model that looks like this: public interface IEntity { int Id { get; set; } } Then the idea is to have my entities inherit from this interface:
I like the way NCommon saves me from dealing with all the plumbing required to do DDD with NHibernate.
I am trying to practice the model first approach and I am putting together a domain model. My requirement is pretty simple: UserSession can have multiple ShoppingCartItems.
Having used DDD for a web site and finding it to be a neat approach, I\'m wond开发者_StackOverflowering if this can/should be applied to desktop applications? Also, with the classes being separated in
I have an NH query which returns a Product with a BasePrice. Depending on various other factors, such as Manufacturer price markup, I use a PricingService on the C# side of things to produce a \"final
Hye! I have Aggregate object that have more than one level. Aggregate root is Network object and it have collection of Nodes and Links. Node and Link have collection of Segments, and Segment have col
I have a question about DDD.I\'m building a application to learn DDD and I have a question about layering. I have an application that works like this:
I am developing a spring mvc based application. I have a simple pojo form object, the problem is that many properties will be taked from drop down lists that are pop开发者_运维技巧ulated from lookup e
I have created a factory and a set of specifications to create and validate an aggregate root.Currently I have some tests for the factory that call the specifications on the product of the factory, bu