Currently if you take a look at the HibernateEntityLogicImpl.java, you'll see this for the discrimiator column and type:
/** * @see org.andromda.cartridges.hibernate.metafacades.HibernateEntity#getHibernateDiscriminatorColumn() */ protected String handleGetHibernateDiscriminatorColumn() { return "class"; } /** * @see org.andromda.cartridges.hibernate.metafacades.HibernateEntity#getHibernateDiscriminatorType() */ protected String handleGetHibernateDiscriminatorType() { return "string"; } If you had a namespace property to define these values, the defaults could be configured at the cartridge level, you could then have 2 tagged values that allowed you to override these defaults where necessary. Why would you want to express the discriminator in the model...its completely a Hibernate dependant implementation detail..thats why a namespace property would be appropriate for defaults and tagged values to override where necessary. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2314#2314 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
