Michael Hunger wrote: > What about separating the relevant parts in Input and Output?
See my response to Tonny: yes, splitting the UI layer into two or three, so that the active controllers and passive view is separated, is probably a good idea! > 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. I think so, yes. Alistair also talks about how systems like this can be more easily hooked up, with output from one part being input for another. > What also comes into my mind is whaty they call "domain object" in POSA 4 > which is a kind of module in our view. That might be. I have yet to read it.. it's on my (looong) reading list though... > I should have done a qi4j tutorial here. Silly me :( Yeah, that'd been nice. Oh well, next time! :-) /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
