[
http://issues.ops4j.org/browse/QI-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583#action_13583
]
Niclas Hedhman commented on QI-247:
-----------------------------------
Yes this is a correct issue, and I presume that the documented support fell out
of the loop in one or the other of the large re-writes that has occurred.
I am re-introducing the following behavior (for ver 1.2);
Equals; If the number of mixins are not identical, return false. Otherwise,
call the equals() method in each mixin, and if all returns true, then return
true. The CompositeMixin will be ignored.
HashCode; Each mixin's hashCode will be called and accumulated as "hash =
hash*31 + mixin.hashCode()". The CompositeMixin will be ignored.
ToString; For each mixin, if the toString() method's declaring class is NOT
java.lang.Object, call it and comma-separate the output across the mixins.
> Broken delegation of Object methods in TransientComposite
> ---------------------------------------------------------
>
> Key: QI-247
> URL: http://issues.ops4j.org/browse/QI-247
> Project: Qi4j
> Issue Type: Bug
> Components: Core Runtime
> Affects Versions: 1.0, 1.1
> Reporter: Lukasz Zielinski
> Assignee: Niclas Hedhman
> Attachments: tests.zip
>
>
> I encountered problems with TransientComposite and custom implemetation of
> Object methods (hashCode, equals, toString) - delegation does not happen as
> described in Complete Manual (http://www.qi4j.org/qi4j/261.html).
> Another thing I noticed is that composite instance is not equal to itself
> when using equals method.
> Tests were run against 1.0 and trunk.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
