yes, thanks David. You are right, its view centric approach for now, which is not pure OO. I meant to say the starting point in my application. Where is shows a list of ABC. That the starting view users may want to see and than they can drill down to (if there is a way provided) how ABC is related to other stuff and that process can continue. I think, in practical terms, when you already have full blown database with years of data, you start picking your domain objects and relationships based on what you want to use in your application and continuously refine those to fit the user needs. I dont know what the most accurate approach would be to build applications (using isis) for such cases. Would you write a complete domain model for my existing database and go from there? or you just start from what you need and keep it growing as per need.
On Wed, Feb 19, 2014 at 10:17 PM, [email protected] <[email protected]>wrote: > Hi Satyendra, > > There is no such concept as a top level domain object in an oo domain > model. I suspect you are starting in the wrong place. You might have in > your mind what should be a view object which is a bad place to start > building your domain. > > David. > > Sent from Yahoo Mail on Android > >
