When removing a JCR workspace via workspace.remove(wsName) not only the workspace itself should be deleted, but also all the nodes below that workspace. Currently if a workspace is deleted and then re-created with the same name, all its former nodes are still accessible. This should not happen.
K. Bachl <korbinian.bachl> made a comment on jira MODE-2009 Hello Horia, Hello Randall, can you please also check the Workspace.clone() operations? It turns out that this also seems affected, as if I import a new workspace and then clone this into another workspace, the old content there isn't emptied correctly right before, leading to all kinds of stale data and JCR integrity exceptions (funny when you want to overwrite it...) or stale data returning as it seems some nodes then appear duplicate etc;
K. Bachl <korbinian.bachl> made a comment on jira MODE-2009 wrong field entered content - sorry;
Cherry-picked from community branch & fixed conflicts: https://github.com/jboss-integration/modeshape/commit/69b69582c8c13b2e2f9ff81e0b2a39a99cf5b049
Fixed before GA - setting to requires_doc_text- accordingly
Verified. After adding a new workspace with node and recreating the workspace, the nodes of the initial created workspace are no longer present.