Share Hibernate Metafacades
---
Key: HIB-136
URL: http://jira.andromda.org/browse/HIB-136
Project: Hibernate Cartridge
Type: Improvement
Versions: 3.1-RC1
Reporter: Luís Miranda
Assigned to: Carlos Cuenca
The org.andromda.cartr
Share Hibernate Metafacades
---
Key: HIB-135
URL: http://jira.andromda.org/browse/HIB-135
Project: Hibernate Cartridge
Type: Improvement
Versions: 3.1-RC1
Reporter: Luís Miranda
Assigned to: Carlos Cuenca
The org.andromda.cartr
finder methods returning Iterator
-
Key: HIB-137
URL: http://jira.andromda.org/browse/HIB-137
Project: Hibernate Cartridge
Type: Improvement
Versions: 3.1-RC1
Reporter: Walter Itamar Mourão
Assigned to: Carlos Cuenca
[ http://jira.andromda.org/browse/HIB-136?page=history ]
Chad Brandon reassigned HIB-136:
Assign To: Chad Brandon (was: Carlos Cuenca)
> Share Hibernate Metafacades
> ---
>
> Key: HIB-136
> URL: http://jira.andr
[ http://jira.andromda.org/browse/HIB-136?page=history ]
Chad Brandon closed HIB-136:
Resolution: Fixed
Fix Version: 3.1
> Share Hibernate Metafacades
> ---
>
> Key: HIB-136
> URL: http://jira.andromda.org/
[ http://jira.andromda.org/browse/HIB-2?page=comments#action_12145 ]
Jaka Jaksic commented on HIB-2:
---
I'm not sure I understand this correctly, but is this solution any better than
picking the inverse association end at random? (Decision based on name len
[ http://jira.andromda.org/browse/HIB-2?page=comments#action_12146 ]
Jaka Jaksic commented on HIB-2:
---
Alternatively, I think the "aggregate" class in the association should be in
control of the collection in most cases, meaning that the opposite associati
