[
https://issues.apache.org/jira/browse/CAY-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik updated CAY-1727:
---------------------------------
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).
was:
One possible scenario (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).
> Modeler thinks entity is using inheritance when it doesn't
> ----------------------------------------------------------
>
> Key: CAY-1727
> URL: https://issues.apache.org/jira/browse/CAY-1727
> Project: Cayenne
> Issue Type: Bug
> Components: Modeler
> Affects Versions: 3.1M2, 3.1B1
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
