Unfix AR-822 and defer to AR-1573.

The in-transaction work has to align with the work that will be done by the actual background archival,
but node archival doesn't fully support all model constructs and associated behaviour.
Instead of continuing to hack away at each issue that comes up, a complete archive rethink is in order.


git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@6154 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Derek Hulley
2007-07-04 11:05:15 +00:00
parent da4677218e
commit 096729effc
14 changed files with 50 additions and 878 deletions

View File

@@ -287,19 +287,12 @@ public interface NodeService
* All associations (both children and regular node associations)
* will be deleted, and where the given node is the primary parent,
* the children will also be cascade deleted.
* <p>
* Depending on the node's type, the presence of certain aspects, the
* node's store or the any other factors determined by the implementation,
* the node may not actually disappear immediately. It may be lined up for
* archival or later deletion.
*
* @param nodeRef reference to a node within a store
* @return Returns <tt>true</tt> if the node was completely removed, otherwise
* <tt>false</tt> if the node will still exist after the call.
* @throws InvalidNodeRefException if the reference given is invalid
*/
@Auditable(key = Auditable.Key.ARG_0 ,parameters = {"nodeRef"})
public boolean deleteNode(NodeRef nodeRef) throws InvalidNodeRefException;
public void deleteNode(NodeRef nodeRef) throws InvalidNodeRefException;
/**
* Makes a parent-child association between the given nodes. Both nodes must belong to the same store.