The handleSubmitOrder chain is triggered when OrderFulfiller receives a SubmitOrder message. The purpose of this chain is to load the order, verify that the order should be fulfilled, divide it up among appropriate fulfillers, and deliver the necessary information to each fulfiller. This chain is triggered when OrderFulfiller receives a SubmitOrder message.
The following sections describe each processor in the pipeline chain.
extractOrderId
Attempts to extract the ID of the order from the OrderId property of the SubmitOrder message.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
handleRetrieveOrder
Determines the method by which the Order should be loaded. If the order ID was successfully extracted in the extractOrderId processor, then moves to the loadOrder processor.
If the order ID was not extracted successfully, then check the LookUpOrderIdFromOrder property of the OrderFulfiller. If this property is true, the chain moves to the loadSaveOrder processor. If this property is false, then the processor throws an InvalidParameterException and chain execution stops.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
loadSaveOrder
Checks to see if the Order exists in the order repository, using the OrderExists method of OrderManager and the ID of the serialized order within the SubmitOrder message as the parameter. If the order exists, the processor loads the order. If the order does not exist, then fulfillment is using a different repository than the order placement system. The processor then saves the order from the message into the repository. In either case, the chain then moves to the verifyOrderForFulfillment processor.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
loadOrder
Loads the order from the order repository. Control then passes to verifyOrderForFulfillement.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
verifyOrderForFulfillment
Calls the verifyOrderFulfillment method of OrderFulfillmentTools, which checks to make sure the order is in a valid state for fulfillment: not INCOMPLETE, PENDING_REMOVE, REMOVED, or NO_PENDING_ACTION.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
splitShippingGroupsFulfillmentChain
Runs splitShippingGroupsFulfilllment chain.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
executeFulfillOrderFragmentChain
Iterates through the shipping groups, and runs executeFulfillOrderFragment chain for each.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
updateOrderRepository
Updates the order in the repository with any changes that may have been made during the execution of this chain (splitting of shipping groups, update of states, etc.).
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
sendModifyOrderNotification
This processor sends a ModifyOrderNotification message with the list of modifications performed during the execution of this chain using JMS.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | None. This is the last link in the chain and causes the |
