Associations generated as Collections
-------------------------------------
Key: SPRING-82
URL: http://jira.andromda.org/browse/SPRING-82
Project: Spring Cartridge
Type: Bug
Versions: 3.1M1
Environment: Windows 2000 Pro, JVM 1.4.2_05, Maven 1.0.2
Reporter: Thad Smith
Assigned to: Chad Brandon
Using the Spring/Hibernate cartridge the default type for assocations is
Collection instead of Set as it was in 3.0.
This creates a problem if a class has a required 1..* association to another
class without any internal attributes. The DAO that is generated doesn't
compile since it is generated with two create methods that take a Collection as
it's argument.
Setting the "hibernateAssociationCollectionType" namespace property for the
hibernate cartridge to "set" in the andromda.xml file has no effect.
Setting the "@andromda.hibernate.collection.type=set" tagged value for the
multiple end of the association has no effect either.
Setting the "specificCollectionInterfaces" namespace property for the hibernate
cartridge results in more compile time errors.
For more information see the following discussion:
http://galaxy.andromda.org/forum/posting.php?mode=reply&t=215
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
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-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
