org.squashtest.csp.tm.internal.service
Interface CampaignNodeDeletionHandler

All Superinterfaces:

NodeDeletionHandler<CampaignLibraryNode,CampaignFolder>

All Known Implementing Classes:

CampaignDeletionHandlerImpl

public interface CampaignNodeDeletionHandler
extends NodeDeletionHandler<CampaignLibraryNode,CampaignFolder>

The following specialization for NodeDeletionHandler, meant for the campaigns, will also handle the deletion of campaign related entities like Iterations and Executions. Thus the contract of the interface NodeDeletionHandler is extended for those entities. First, some definitions :

• Targeted deletion : the user designated one or several entities to be specifically deleted
• Cascaded deletion : the entities that become deleted due to the cascade mechanisms (initiated by a targeted deletion higher in the hierarchy

In the context of a targeted deletion, Iterations and Executions may require a preview of the deletion operation just like the other library nodes, so they both a simulateIterationDeletion and simulateExecutionDeletion methods, which both obey to the same specifications than NodeDeletionHandler.simulateDeletion(List). However, while Iterations are candidates to mass-deletion, Executions are always deleted one at a time. That's why deleteExecution(Execution) have a different contract to enforce this. On the other hand, in the context of a cascade deletion both Iterations and Executions will be removed en masse. Further remarks : The disassociation an IterationTestPlanItem from an Iteration is already handled by IterationTestPlanManager. However the implementation of this interface should also take care of these entities in the context of a cascade removal. Same remark goes for CampaignTestPlanItem.

Author:

bsiri

Method Summary

void	deleteExecution(Execution execution) that method should delete the execution.
List<Long>	deleteIterations(List<Long> targetIds) that method should delete the iterations.
List<SuppressionPreviewReport>	simulateExecutionDeletion(Long execId) that method should investigate the consequences of the deletion of the given executions, and return a report about what will happen.
List<SuppressionPreviewReport>	simulateIterationDeletion(List<Long> targetIds) that method should investigate the consequences of the deletion of the given iterations, and return a report about what will happen.

Methods inherited from interface org.squashtest.csp.tm.internal.service.NodeDeletionHandler

deleteNodes, simulateDeletion

Method Detail

simulateIterationDeletion

List<SuppressionPreviewReport> simulateIterationDeletion(List<Long> targetIds)

that method should investigate the consequences of the deletion of the given iterations, and return a report about what will happen.

Parameters:

targetIds -

Returns:

deleteIterations

List<Long> deleteIterations(List<Long> targetIds)

that method should delete the iterations. It still takes care of non deletable iterations so the implementation should filter out the ids that can't be deleted.

Parameters:

targetIds -

Returns:

the list of the ids of the iterations actually deleted.

simulateExecutionDeletion

List<SuppressionPreviewReport> simulateExecutionDeletion(Long execId)

that method should investigate the consequences of the deletion of the given executions, and return a report about what will happen.

Parameters:

targetIds -

Returns:

deleteExecution

void deleteExecution(Execution execution)

that method should delete the execution. It still takes care of non deletable executions so the implementation should abort if the execution can't be deleted.

Parameters:

targetIds -

Throws:

RuntimeException - if the execution should not be deleted.