cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Drabenia (JIRA)" <>
Subject [jira] [Updated] (CAY-1727) Modeler thinks entity is using inheritance when it doesn't
Date Tue, 04 Dec 2012 12:28:58 GMT


Ilya Drabenia updated CAY-1727:

    Attachment: CAY-1727.patch
> Modeler thinks entity is using inheritance when it doesn't
> ----------------------------------------------------------
>                 Key: CAY-1727
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Modeler
>    Affects Versions: 3.1M2, 3.1B1
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1B2, 3.2M1
>         Attachments: CAY-1727.patch
> 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
For more information on JIRA, see:

View raw message