[ http://jira.andromda.org/browse/HIB-173?page=all ]
Carlos Cuenca closed HIB-173:
-----------------------------
Fix Version: 3.2-RC1
Resolution: Fixed
Now aggregation and composition is taken into account to determine the inverse
attribute. If no one of them is found, the longer name will determine it.
> many2many inverse
> -----------------
>
> Key: HIB-173
> URL: http://jira.andromda.org/browse/HIB-173
> Project: Hibernate Cartridge
> Type: Improvement
> Versions: 3.1
> Reporter: Darius Schier
> Assignee: Carlos Cuenca
> Fix For: 3.2-RC1
>
> Hi there,
> until now many2many associations added the inverse flag at that side which's
> side was lexically longer. By a minor change within hibernate's association
> end locig implementation, the behaviour could be more deterministic:
> protected boolean handleIsHibernateInverse()
> {
> // inverse can only be true if the relation is bidirectional
> boolean inverse = this.isNavigable() &&
> this.getOtherEnd().isNavigable();
> if (inverse)
> {
> inverse = this.isMany2One();
> if (this.isMany2Many() && !inverse)
> {
> inverse = isAggregation() || isComposition();
> }
> }
> return inverse;
> }
> Setting the values at the "diamond's" side should be enough (which could be a
> matter of discussion of course).
--
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
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
