Bug 1048153 - NodeIterator.hasNext() method returns wrong results
Summary: NodeIterator.hasNext() method returns wrong results
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: ModeShape
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: CR2
: 6.0
Assignee: Horia Chiorean
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-03 09:58 UTC by Horia Chiorean
Modified: 2016-02-10 08:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When using the hierarchical database API, NodeIterator.hasNext() is advancing the iterator in some circumstances. To workaround this issue, call session.save() before calling the hasNext() method.
Clone Of:
Environment:
Last Closed: 2016-02-10 08:51:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker MODE-2126 0 Major Closed NodeIterator.hasNext() method returns wrong results 2014-02-13 14:45:41 UTC

Description Horia Chiorean 2014-01-03 09:58:44 UTC 
According to API , NodeIterator.hasNext() method should return same result if next() method is not called meanwhile. This is not the case in some situations, when I do some node adding combined with calling clone().
Comment 2 JBoss JIRA Server 2014-01-07 17:46:05 UTC 
Randall Hauch <rhauch> updated the status of jira MODE-2126 to Closed
Comment 3 belong 2014-01-08 06:20:35 UTC 
Horia confirmed fixed for CR2 - setting to requires_doc_text- accordingly.
Note You need to log in before you can comment on or make changes to this bug.