The handleModifyOrderNotification chain is triggered by OrderFulfiller receiving a ModifyOrderNotification message.
The following sections describe each processor in the pipeline chain.
extractOrderId2
This processor attempts to extract the ID of the order from the OrderId property of the ModifyOrderNotification message.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
loadOrder2
This processor loads the order from the order repository.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
handleModificationClassType1
Determines if the modifications listed in the ModifyOrderNotification message are valid. If so, it calls the appropriate processor chains, and upon conclusion, passes control to the updateOrderRepository2 processor. Possible chains that ModifyOrderNotification modifications could trigger are handleIdTargetModification, handleShipGroupUpdateModification, and handlePayGroupUpdateModification.
If a modification listed is not valid, then the chain moves on to the modificationNotSupported3 processor.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
modificationNotSupported3
This processor currently does nothing. Control then passes to updateOrderRepository1.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | Return value of 1 executes the |
updateOrderRepository2
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 |
sendModifyOrderNotification2
If any modifications were made during the execution of this chain, this processor sends a ModifyOrderNotification message with the list of modifications using JMS.
Transactional Mode | TX_MANDATORY |
Component |
|
Object |
|
Transitions | None. This is the last link in the chain and causes the |
