[CAY-1727] Modeler thinks entity is using inheritance when it doesn't

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1M2, 3.1B1
• Fix Version/s: 3.1B2, 3.2.M1
• Component/s: Modeler
• Assignee: Andrus Adamchik
• Reporter: Andrus Adamchik
• Created: 21/Jul/12 20:02
• Updated: 04/Dec/12 17:37
• Resolved: 04/Dec/12 17:37

Description

The modeler mixes up Java inheritance with "persistent inheritance", which I guess can be confusing indeed.

One possible scenario to reproduce (I think this is not limited to these steps) :

• Create new DataMap, enter arbitrary custom superclass
• Create DbEntity with a couple of columns
• Click "Create ObjEntity" that will create a new ObjEntity based on this DbEntity

The resulting ObjEntity "Table/View" field is disabled. The Modeler thinks that custom superclass corresponds to persistent inheritance... Deleting it, going to some other entity, and then returning back to this ObjEntity will reactivate "Table/View".

"Table/View" should be disabled only when "Inheritance" dropdown is populated (i.e. when "super entity" is chose, not just a superclass).