What about separating the relevant parts in Input and Output? That reminds me also of Holubs Importer/Exporter Pattern that was discussed on the DDD list (if I remember correctly). So having the OUTPUT consume external domain (exporter entity mixins, interfaces, services, ...) and the input populate them using this kind of separation of import and export for external components outside of the domain layer. perhaps this also matches quite well with the domain consuming and sending messages (message entities?) in greg yougs DDDD.
What also comes into my mind is whaty they call "domain object" in POSA 4 which is a kind of module in our view. Having fun at qcon I should have done a qi4j tutorial here. Silly me :( Michael _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
