org.squashtest.tm.service.internal.deletion
@Component(value="squashtest.tm.service.deletion.RequirementNodeDeletionHandler") public class RequirementDeletionHandlerImpl extends AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder> implements RequirementNodeDeletionHandler
| Constructor and Description |
|---|
RequirementDeletionHandlerImpl() |
| Modifier and Type | Method and Description |
|---|---|
protected OperationReport |
batchDeleteNodes(List<Long> ids)
Will delete the nodes identified by the ids parameter.
|
OperationReport |
deleteNodes(List<Long> targetIds)
|
protected List<Long> |
detectLockedNodes(List<Long> nodeIds)
Given a list of node ids, returns a sublist corresponding to the ids of the nodes which cannot be deleted according to the specs.
|
protected List<SuppressionPreviewReport> |
diagnoseSuppression(List<Long> nodeIds)
Given their ids, that method should check the nodes and actually report the informations as specified in
NodeDeletionHandler.simulateDeletion(List). |
protected FolderDao<org.squashtest.tm.domain.requirement.RequirementFolder,org.squashtest.tm.domain.requirement.RequirementLibraryNode> |
getFolderDao()
The implemention should return which FolderDao to use depending on the end domain object.
|
findNodeHierarchy, findPairedNodeHierarchy, simulateDeletionclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitsimulateDeletionprotected FolderDao<org.squashtest.tm.domain.requirement.RequirementFolder,org.squashtest.tm.domain.requirement.RequirementLibraryNode> getFolderDao()
AbstractNodeDeletionHandlergetFolderDao in class AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>protected List<SuppressionPreviewReport> diagnoseSuppression(List<Long> nodeIds)
AbstractNodeDeletionHandlerGiven their ids, that method should check the nodes and actually report the informations as specified in NodeDeletionHandler.simulateDeletion(List).
See AbstractNodeDeletionHandler.detectLockedNodes(List) for details regarding the input list.
diagnoseSuppression in class AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>nodeIds - the complete list of the nodes involved in that report.protected List<Long> detectLockedNodes(List<Long> nodeIds)
AbstractNodeDeletionHandlerGiven a list of node ids, returns a sublist corresponding to the ids of the nodes which cannot be deleted according to the specs. The input list includes all the nodes and their children in the directory structure. The implementation is responsible to fetch any other dependencies needed for the completion of its task. The implementation is not required to resolve which folders are locked : this abstract class will handle that on the basis of the returned value.
detectLockedNodes in class AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>nodeIds - all the node ids.public OperationReport deleteNodes(List<Long> targetIds)
AbstractNodeDeletionHandlerdeleteNodes in interface NodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>deleteNodes in class AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>targetIds - the list of node ids selected by the user.protected OperationReport batchDeleteNodes(List<Long> ids)
AbstractNodeDeletionHandlerbatchDeleteNodes in class AbstractNodeDeletionHandler<org.squashtest.tm.domain.requirement.RequirementLibraryNode,org.squashtest.tm.domain.requirement.RequirementFolder>ids - the doomed node ids.Copyright © 2010-2014 Henix, henix.fr. All Rights Reserved.