Issue Details (XML | Word | Printable)

Key: JSR_283-791
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: jsr-283-issues
Reporter: anchela
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Expected behaviour of Node.getReferences/getWeakReferences if Node not referenceable

Created: 01/Jul/09 01:24 AM   Updated: 07/Jul/09 11:59 PM   Resolved: 07/Jul/09 11:59 PM
Component/s: javadoc/api
Affects Version/s: current
Fix Version/s: milestone 1

Time Tracking:
Not Specified


Operating System: All
Platform: All

Issuezilla Id: 791
Participants: anchela, jsr-283-issues and Peeter Piegaze

 Description  « Hide

The RI returned an empty PropertyIterator when Node.getReferences was
called on a Node that isn't referenceable.

However, Node.getWeakReferences threw UnsupportedRepositoryOperation which
i modified to empty PropertyIterator as well [1].

As stated in the issue, i had a quick look at the javadoc and couldn't find
what was the expected behavior.

Not throwing feels better to me and i would suggest to state that in the
method description.
(I didn't check the specification though...)



Peeter Piegaze added a comment - 02/Jul/09 01:23 PM

chnaged platform

Peeter Piegaze added a comment - 06/Jul/09 12:31 PM

Clarified that both getReferences and getWeakreferences must return an empty iterator in all cases where
this node has no referring (weak)reference properties, including the case where this node is not

Issues left open until fixed in RI

anchela added a comment - 07/Jul/09 11:59 PM

issue JCR-2177 has been fixed including adding tests to the TCK for both references and weakreferences/