at the same type I don't like objects which have fields which are unused or have no meaning if a discriminant has some value, it makes debugging harder and the model harder to understand. we'll find the right balance. "chris.laprun(a)jboss.com" wrote : "sohil.shah(a)jboss.com" wrote : anonymous wrote : | | | There are also other valid points that makes me prefer a hierarchy over an objects that aggregates all: | | | | | | - easier to debug | | | - easier to categorize | | | - inheritance and polymorphism can be leveraged | | | | | | | These are actually valid points. | | | | I am more concerned about the hierarchy overload from the standpoint of what objects are used/exposed to the Controller layer as it integrates with the UI Server. | | | | Same here. I tend to prefer a generic object to handle as much as possible with only minimal sub-classes as required. As far as debugging goes, toString is our friend: as long as we have enough information in the object (and we should), we should be able to have a toString method that could be leveraged while debugging. | | I don't like huge hierarchy of weak objects (objects that don't do much, if anything at all, and we do have some objects like that)... They result in lots of classes with no obvious benefits. Inheritance and polymorphism works well for worker objects, not so much for data objects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061516#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...