Class EsbOperateStep
java.lang.Object
com.kingsrook.qqq.esb.processes.EsbOperateStep
- All Implemented Interfaces:
BackendStep
- Direct Known Subclasses:
EsbDeleteMessagesMetaDataProducer.Step,EsbMoveMessagesMetaDataProducer.Step,EsbPauseQueueMetaDataProducer.Step,EsbPauseTriggerMetaDataProducer.Step,EsbPurgeQueueMetaDataProducer.Step,EsbReplayDeadLettersMetaDataProducer.Step,EsbRestartTriggerMetaDataProducer.Step,EsbResumeQueueMetaDataProducer.Step,EsbResumeTriggerMetaDataProducer.Step
Server-side permission boundary and implementation for ESB operations.
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidrun(RunBackendStepInput input, RunBackendStepOutput output) Execute the backend step - using the request as input, and the result as output.
-
Constructor Details
-
EsbOperateStep
public EsbOperateStep()
-
-
Method Details
-
run
Description copied from interface:BackendStepExecute the backend step - using the request as input, and the result as output. TODO - think about - why take the Result object as a param, instead of return it? Is this way easier for inter-language operability maybe? Also - there's way too much "process-specific gunk" in the Request object - can we simplify it?- Specified by:
runin interfaceBackendStep- Throws:
QException
-