> in order to generate diferent collections, you should use the tagged > value "@andromda.hibernate.collection.type" > also for ordered collections, you should specify the > "@andromda.hibernate.collection.index" the determine the attribute that > will be used for indexing
As I said, I've set this tagged value to "set" on a few association ends in my model. But in the generated code, I still have java.util.Collection's generated whereas it should be java.util.Set ! Is there some kind of a bug with this tagged value in AndroMDA RC1 or do I make something wrong ? -- Sebastien ARBOGAST ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
