Bug 780186 (SOA-2562) - FileSystemConnector does not process rename node properly after commit
Summary: FileSystemConnector does not process rename node properly after commit
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2562
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER5
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 12:01 UTC by Jiri Pechanec
Modified: 2011-01-06 11:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-06 11:31:06 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780045 0 high CLOSED FileSystemConnector does not process rename node properly between commits 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker MODE-1010 0 None None None Never
Red Hat Issue Tracker SOA-2562 0 None None None Never

Internal Links: 780045

Description Jiri Pechanec 2010-11-10 12:01:49 UTC 
project_key: SOA

This code does not work
		Node root = session.getRootNode();
		Node old = root.addNode("oldname", "nt:folder");
		session.save();
		session.move("/oldname", "/newname1");		
		session.save();

The second save throws an exception
        javax.jcr.InvalidItemStateException: Unable to find "/{}newname1"; lowest existing path is "/"
        at org.modeshape.jcr.SessionCache.save(SessionCache.java:410)
        at org.modeshape.jcr.JcrSession.save(JcrSession.java:1397)

The 'oldname' directory exists on the disk.

The issue appeared after resolution of SOA-2408
Comment 1 Jiri Pechanec 2010-11-10 12:02:18 UTC 
Link: Added: This issue is related to SOA-2408
Comment 2 Van Halbert 2010-11-10 14:07:13 UTC 
Link: Added: This issue Cloned to SOA-2564
Comment 3 Van Halbert 2010-11-10 20:27:31 UTC 
Changes have been committed to the 2.2.x product branch and should be in the ER5 release.
Comment 4 Jiri Pechanec 2011-01-06 11:31:06 UTC 
Verified in ER6
Note You need to log in before you can comment on or make changes to this bug.