[ http://jira.andromda.org/browse/HIB-169?page=comments#action_12440 ]
Cédric Vidal commented on HIB-169:
----------------------------------
Don't you have some inconsistencies using both ?
Except maybe if you implement getCs() that way:
public Collection getCs() {
Collection as = this.getAs();
Collection cs = new ArrayList();
for(Iterator i = as.iterator(); i.hasNext(); ) {
A a = (A)i.next;
C c = a.getC();
cs.add(c);
}
return
org.apache.commons.collections.CollectionUtils.unmodifiableCollection(cs);
}
As I see it, the cs collection has to be unmodifiable, because, if you add or
remove a C without taking care of the matching A, you could end up with an
unconsistent DDL.
What do you map in the hibernate mapping file, the As, the Cs or both ?
> Take into account association classes
> -------------------------------------
>
> Key: HIB-169
> URL: http://jira.andromda.org/browse/HIB-169
> Project: Hibernate Cartridge
> Type: Improvement
> Versions: 3.1
> Reporter: Cédric Vidal
> Assignee: Carlos Cuenca
>
> Association classes support has been added to UML metafacades, but are not
> yet taken into account in the java files and hibernate mapping files
> generated by the hibernate cartridges.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
