The handleOrderWaitingShipMap
chain is executed when called by the handleHardgoodUpdateInventory
chain.
The following sections describe each processor in the pipeline chain.
lockMessage
This processor uses the ClientLockManager
to guarantee that only one thread dealing with a message for a given key is running through the system at any moment in time. The key used to acquire the lock is returned by the method getKeyForMessage()
.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
loadOrder4
This processor loads the given order from the repository.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
processHardgoodShippingGroupsChain1
This processor iterates through the shipping groups contained in the order, and runs the processHardgoodShippingGroup
chain for each.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
updateOrderRepository4
This processor updates the order in the repository with any changes that may have been made during the execution of this chain.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
sendModifyOrderNotification4
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 |