You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2015/11/09 10:11:11 UTC

[jira] [Commented] (SLING-4565) Override equals/hashcode for JSON entities

    [ https://issues.apache.org/jira/browse/SLING-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996234#comment-14996234 ] 

Timothee Maret commented on SLING-4565:
---------------------------------------

[~sseifert@pro-vision.de] I think you are right wrt to the performance penalty. It makes sense to avoid deep comparison by default. Deep comparison may be provided as an util or extra method. But that's outside the initial scope of this issue. Closing.

> Override equals/hashcode for JSON entities
> ------------------------------------------
>
>                 Key: SLING-4565
>                 URL: https://issues.apache.org/jira/browse/SLING-4565
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons JSON 2.0.10
>            Reporter: Timothee Maret
>
> JSON entities in the package 
> {code}
> org.apache.sling.commons.json
> {code}
> do not yet override the equals and hashCode methods, leaving the equals to compare references rather than the actual content of the entity.
> This issue is about implementing equals/hashCode on those entities in order to allow meaningful comparisons.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)