Ordered Associations should generate appropriate "ordered" collections
----------------------------------------------------------------------
Key: HIB-177
URL: http://jira.andromda.org/browse/HIB-177
Project: Hibernate Cartridge
Type: Bug
Versions: 3.2-RC1
Environment: Hibernate 3.x, Windows XP
Reporter: olaf kruger
Assigned to: Carlos Cuenca
Assocation Ends tagged with "{ordered}" currently generate implementation
collection of HashSets (exposed through a plain Collection interface). This
means that the UML model specification is actually not heeded: the client of
the collection neither knows, nor sees reflected, the fact that the collection
is ordered. In fact, I suspect this is actually buggy as the ordering cannot be
maintain through a HashSet. This comment applies both to the
'@...orderByColumns' as well as the '@...hibernate.collection.list'.
In short: the generated implementation collection should be some specific,
"ordered" collection.
Both the above tags should: be ignored if the assocation end is not ordered
and, secondly, should be mutually exclusive.
For a full description and concluding comments, see:
http://galaxy.andromda.org/forum/viewtopic.php?p=10225#10225
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
