Hi Dan, Yes, I read your DDD book - the recognition and use of color modelling archetypes was very appropriate in that context - it's what led me to NO/ISIS in the first place.
I had no idea this (ISIS) domain object limitation existed in the first place until now - I'll admit I've pushed this discussion to find out why it is a problem for the framework - the only clue I had there may be a problem was the ISIS-743 - admittedly I am still none the wiser as to why but that's my fault for not taking more time to understand the framework. I guess the first thing to do is for me to understand the problem better so I will withdraw from the conversation now and return to it later. Good work on 1.4 release - we hope to upgrade our 1.3 based app in the very near future. Just started using view objects and json layouts - nice and very necessary. Hope I wasn't coming across as overly critical or pessimistic or pedagogue like. If so, I apologize. Regards, David. On Friday, 21 March 2014 8:48 PM, Dan Haywood <[email protected]> wrote: Hi David, Nice to read about the old FDD stuff again. I remember introducing color modelling archetypes to Richard Pawson, and I think they an appearance in his original NO book. I certainly wrote about them myself in my two books on TogetherJ and DDD. So yes, I do get that the domain entities are part of the PD layer, not the UI layer. And I agree that Isis must support the ability to handle domain objects that have no local persistence. But since the two approaches I've suggested aren't palatable, I guess I'm out of ideas... Do you (or anyone else) have any suggestions on how to accomplish this objective? Dan
