jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1535) Some tests assume that an implementation of javax.jcr.Item overrides equals()
Date Tue, 16 Sep 2008 14:18:44 GMT

     [ https://issues.apache.org/jira/browse/JCR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1535:
-------------------------------

    Affects Version/s:     (was: 1.5)
                       1.4
        Fix Version/s: 1.5

> Some tests assume that an implementation of javax.jcr.Item overrides equals()
> -----------------------------------------------------------------------------
>
>                 Key: JCR-1535
>                 URL: https://issues.apache.org/jira/browse/JCR-1535
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>    Affects Versions: 1.4
>            Reporter: Dominique Pfister
>             Fix For: 1.5
>
>
> The following 3 tests (followed by the line number containing the bad assertion):
> org.apache.jackrabbit.test.api.ReferencesTest.testReferenceTarget:135
> org.apache.jackrabbit.test.api.ReferencesTest.testAlterReference:169
> org.apache.jackrabbit.test.api.version.VersionHistoryTest:152
> assume that an implementation of javax.jcr.Item overrides equals(), such that 
> Assert.assertEquals(n1, n2) or 
> java.util.Set.contains(n1) 
> works for two "equal" nodes n1,n2 or for some node n1 that has been previously put into
a set. However, there is no section in the specification that would mandate this. The tests
above should therefore replace assertEquals() with one of the other mechanism that officially
supported, such as javax.jcr.Node.isSame().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message