mkuppe wrote: how does an association to a Class and an attribute of type Class differ in the generated code? Is there a preferred approach here?
(end of quote) you can't use any arbitrary class as the type of an entity attribute with the hibernate cartridge, andromda will print a validation error message telling you only <<Enumeration>> or <<EmbeddedValue>> classes may be used in that way mkuppe wrote: I have read in another thread that it is not supported for Entities to Realize interfaces. Does this also stand for Embedded Values? Can an Entity reference an interface which is Realized by Embedded Values? (end of quote) Yeah, theoretically we could support this, just never needed it. The main reason being that realizing interfaces to generate just that kind of code brings you closer to the PSM layer which we're trying to avoid, on the other hand, it could be supported if there are some good arguments (which I'm assuming you have, since you need it) what is it exactly you are trying to do ? -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1723#1723 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
