This is more of a modeling discussion. Let's say that there's a bunch of paint manufacturing companies and they all want to have their own available paint colors so that customers can pick which color they want from a company. The paint companies can activate or deactivate the colors they are offering. The paint colors are enumerations but specific to their own respective paint company. Usually I would say the paint color would be Value composites since they only make sense under the respective paint company but when it comes to the scenario where the customer is picking the color, it sounds like the paint itself should be an entity.
Usually in the UI, it's a select list or a bunch of radio buttons; when the paint is selected and if the paint is an entity then I can directly use the paint in a transaction but if it was a value composite, I would have to look up the company first and then look for the paint. I've actually done it both ways in previous projects but was never sure if I was following a domain concern or letting the UI drive the model. Any thoughts? Aye _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
