Bug 1048153

Summary: NodeIterator.hasNext() method returns wrong results
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Horia Chiorean <hchiorea>
Component: ModeShapeAssignee: Horia Chiorean <hchiorea>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: fnguyen, ldimaggi, rhauch, vhalbert
Target Milestone: CR2Keywords: QA-Closed
Target Release: 6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:51:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.