My understanding from the discussion on these two jira issues was that using tagged values was incorrect due to the fact that you were putting
hibernate-specific information where it shouldn't be. http://galaxy.andromda.org/jira/browse/HIB-32 http://galaxy.andromda.org/jira/browse/HIB-55 You said: Quote: Actually 2 namespace properties would be appropriate: one to define the name and one to define the type, then you could use 2 tagged values to override the defaults where required (end of quote) What do you mean by "namespace properties"? My understanding of the discriminator is that you need an attribute (column actually), a type and a value. I assume we could derive the type from attribute in the model, but that attribute and the value must be defined somewhere. BTW, what is the possibility of replacing this forum with a normal mailing list? :-P _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2310#2310 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
