I hacked andromda to support defining the hibernate discriminator bits as
tagged values...but then I went to the jira and read that using tagged
values was not the right solution and I agree with the arguments against
the use of tagged values in the model. So _how should_ this be modelled?
I don't know much about UML (yet :-)), but it seems that if we had a
subclass entity that defined an attribute inherited from a superclass as
immutable ("frozen" in MagicDraw terms) and having a default value,
then we could know in the hibernate cartridge that this column was the
discriminator column and value.
Comments?
I've burned my weekend solving this the wrong way, but if I can get
some direction, I'll try to hack out the right solution next weekend.
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2308#2308
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
