In JBoss ESB, the structure of a service consists of a simple action pipeline that is responsible for processing each request in a sequential manner. There are no restrictions placed on the content or structure of the requests or on the functionality that can be exposed through a service.
The service pipeline is the real workhorse of JBoss ESB, responsible for the following:
Controlling the lifecycle of each action
Validation and delivery of the message through the action processors
Generating appropriate responses once the request is complete.
A service can consist of any number of actions, each processing the output from the preceding action in the pipeline.
The pipeline treats each action as if it was an implementation of the org.jboss.soa.esb.actions.ActionPipelineProcessor
interface, containing the lifecycle and processing methods supported by the pipeline. If the service action does not directly implement this interface then the pipeline will create...