Class EnableDisableExecutor
- java.lang.Object
-
- com.evolveum.midpoint.model.impl.scripting.actions.BaseActionExecutor
-
- com.evolveum.midpoint.model.impl.scripting.actions.EnableDisableExecutor
-
- All Implemented Interfaces:
ActionExecutor
@Component public class EnableDisableExecutor extends BaseActionExecutor
Implements "enable" and "disable" actions. It is ObjectType-typed just because it handles both FocusType and ShadowType objects.
-
-
Nested Class Summary
-
Nested classes/interfaces inherited from class com.evolveum.midpoint.model.impl.scripting.actions.BaseActionExecutor
BaseActionExecutor.ItemProcessor
-
-
Field Summary
-
Fields inherited from class com.evolveum.midpoint.model.impl.scripting.actions.BaseActionExecutor
actionExecutorRegistry, cacheRepositoryService, expressionFactory, expressionHelper, matchingRuleRegistry, midpointFunctions, modelService, operationsHelper, prismContext, provisioningService, relationRegistry, schemaService, scriptingExpressionEvaluator, securityContextManager, securityEnforcer, taskService
-
-
Constructor Summary
Constructors Constructor Description EnableDisableExecutor()
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description PipelineDataexecute(ActionExpressionType action, PipelineData input, ExecutionContext context, OperationResult globalResult)Executes given action command.voidinit()-
Methods inherited from class com.evolveum.midpoint.model.impl.scripting.actions.BaseActionExecutor
createVariables, exceptionSuffix
-
-
-
-
Method Detail
-
init
@PostConstruct public void init()
-
execute
public PipelineData execute(ActionExpressionType action, PipelineData input, ExecutionContext context, OperationResult globalResult) throws ScriptExecutionException, SchemaException, ObjectNotFoundException, SecurityViolationException, CommunicationException, ConfigurationException, ExpressionEvaluationException
Description copied from interface:ActionExecutorExecutes given action command.- Parameters:
action- Command to be executed. Its parameters can be defined statically (using "new" specific subclasses in the schema) or dynamically (using "old fashioned" dynamic name-value parameters) or in a mixed style, where dynamic definitions take precedence.input- Input data (pipeline) that the action has to be executed on.context- Overall execution context.globalResult- Global operation result. This is the parent result that receives subresults related to actions executions. (But individual results are stored also into the pipeline, to indicate success/failure of individual pipeline items processing.)- Throws:
ScriptExecutionExceptionSchemaExceptionObjectNotFoundExceptionSecurityViolationExceptionCommunicationExceptionConfigurationExceptionExpressionEvaluationException
-
-