public interface ServiceCommand
AbstractServiceCommand, as it enforces much of the contract that a command must obey.
The ServiceCommand interface is designed such that commands can be executed in two modes: either by calling the authorize/validate/execute methods separately, or by calling execute directly and dealing with authorization or validation failures as exceptions.
A well-behaved service command implementation must:
Service commands are not thread-safe.
|Modifier and Type||Method and Description|
Execute the command.
Gets the list of errors that are preventing the command from being executed.
Determine if the current user is authorized to execute this command.
Determine if the command is in a valid state to be executed.
execute()is be expected to perform successfully (unless prevented by some system error). If this method returns false,
executewill fail with a
This method should be called after checking
isAuthorized(). If the current user is not
authorized to execute this command, this method must throw a
If this method returns false, then
getValidationErrors() must return a non-empty list of
errors explaining why the command was not valid. If this method returns true, the collection returned by
getValidationErrors() must be empty.
isValid()will always return an empty collection.
ValidationErrorobjects describing why command validation failed
Copyright © 2003–2016 Atlassian. All rights reserved.