Thoughts about CAB & Naked Objects (1)

I am having hard time putting in practice the WorkItem or even the MVC/MVP patterns of the Composite Application Block. While starting to read the thesis on the Naked objects, I am wondering if it is not because I am more inclined to the latter approach which emphasis the behavioral completeness of the objects. The separation of concerns sure sounds nice but I am often finding overwhelming to create FooModel, FooController and FooView. In most of the samples you can find in the literature, each object is mostly forwarding request to another and is not really doing anything else.

If I want to display a list of books, I do not feel the need to create a BookListView. I'd rather have a List, and a way to bind anything to it, Books or Authors. It does not matter to me.

Leave a comment

Please note that we won't show your email to others, or use it for sending unwanted emails. We will only use it to render your Gravatar image and to validate you as a real person.