I wanted to make sure I'm not doing something wrong here before I open up a defect, since I'm new to the changes from 3.0 to 3.1.
I have two classes: ------- 1 1..* ----------------- | Foo |<>--------> | Bar | ------- | +name: String | ----------------- In 3.0 the relationship to Bar in Foo was generated as a Set. In 3.1-M1-SNAPSHOT it is generated as a Collection using a HashSet. The problem is that Foo has no other required attributes and FooDAO.java now has two create methods that take only a Collection. The first takes a Collection of Foo's to persist. The second takes a Collection of Bar's to create a new Foo with! Obviously I could add another required attribute to Foo to fix the problem, but that's not what I want to do. I tried adding the hibernateAssociationCollectionType property in the andomda.xml file that was generated by the andromdapp Maven plugin: <property name="hibernateAssociationCollectionType">set</propery> I added this to both the Spring and Hibernate plugin sections without any luck! I then tried to override it at the association level by setting the tagged value: @andromda.hibernate.collection.type=set, but the relation was still generated as a Collection. Regards, Thad Smith _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1124#1124 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
