Actually, I did make the discriminator work with joined-subclass, so this is really just a matter of deciding how to model this concept.
I would really like to model this as in the model linked above, where the inherited "type" attribute is set to an immutable default value by the subclass. We could know to implement the model with the hibernate discriminator under these conditions. I think it would be fairly straightforward, because we'd have the column, type and value all from the model. The fact that the hibernate cartridge implemented this as a discriminator would be properly hidden from the model. Could this be modelled as an OCL? I looked at OCL a while today, but it was a bit more than I could wrap my head around without a larger corpus of examples than what I found... Thoughts? cheers. b _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2347#2347 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
