<div dir="ltr"><div class="message-actions weak-color">
<p class="message-actions1">
<<David Mitchell-10
<span id="nabble.descriptor19031898"></span>
</p>
</div>
Start with Object.
<br><br>I usually create my own "Model" base class for my application
<br>(subclass of Object). I have an application right now called Epic, so
<br>I have an EpicModel. It makes a convenient home for shared
<br>functionality.
<br><br>Don't fall into the trap of subclassing collections. You almost always
<br>want your domain object to have a collection, not be a collection.
<br><br>It has been rare in my applications to have domain models that are
<br>subclasses of something already in the image. Honestly can't think of
<br>it happening once (though I'm sure that it has).
<br><br>The domain is one place where you can be really clean. You usually
<br>don't have that luxury in the presentation, controller, persistence,
<br>etc.
>><br><br><br><FX: sound of new subclassed collection being quietly deleted! > ;-)<br><br>Thanks guys, that's very helpful. I shall follow your advice<br><br>Cheers<br>AB<br></div>