The original idea was to use the DDD concept for aggregate, as described briefly http://fornax.itemis.de/confluence/display/fornax/3.+Advanced+Tutorial+(CSC)#3.AdvancedTutorial(CSC)-Aggregate here .
You can define 'not aggregateRoot' on an Entity to indicate that it belongs to a parent aggregate. Maybe that is not enough. Maybe we should make it possible to define aggregation on reference also. /Patrik PaloT wrote: > > Yes, we need information if relation is "association" or > "aggregation". I will need this kind of information also in > smartclient. For now I'm recognizing it by existence of service. If > service exist (it is independent entity) than it's association, > otherwise is aggregation. Is here some better way how to recognize > type of relation? > > Pavel > -- View this message in context: http://www.nabble.com/Hiberanate-Cascade-Delete-Issue-in-many-to-many-relationship-tp26080397s17564p26110330.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
