Qi4j beautifully makes it possible to separate state and behaviour. And even generic behavior like an Assignable; "assign GenericA to GenericB" (as shown in Rickards excellent presentation http://oredev.org/prod/oredev/site.nsf/docsbycodename/session?opendocument&sid=88EF79931A074A1AC125759A003AB0ED&track=24116556E47101EAC12575A50049A141&day=5).
Doesn't this rock the DDD boat some (in a great way!) in the sense that the "classical" BC/Module/AR/Entity boundaries would have the behavior dimension extracted into "Cross cutting (domain?) behavior"?! I'm trying to dive into the new paradigm and to practically organize my folder/package structure accordingly. I have read heated discussions about bounded contexts etc in the DDD Yahoo group, and I wonder if/how you qi4j folks are physically/conceptually organizing the behavioral part (used across domain contexts) in larger applications (with several BC's)? Or, simply put: where does generic behavior belong? What differences are there in organizing a project namespace in DCI and in DDD (if you can put them up against each other). Any directory structure examples would be much appreciated. I was originally planning to post this in the Yahoo DDD group, but I find that they are a little slow to pick up on the powers of qi4j :) so I imagined the subject would fit better here... -- View this message in context: http://old.nabble.com/Qi4j-rocking-the-DDD-boat--tp27812017p27812017.html Sent from the Qi4j-dev mailing list archive at Nabble.com. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
