The actual loading of an Order object occurs by calling the loadOrder() method in the OrderManager. The loadOrder() method calls into the PipelineManager to execute the loadOrder pipeline, which creates and populates the Order object.
The following table describes the individual processors in the loadOrder pipeline. They are listed in order of execution.
PipelineLink name | Description |
|---|
loadOrderObject
| Given an Order ID supplied by the PipelineManager, this processor creates an Order object and loads its properties from the Order Repository. Note that while the Order object is loaded, none of the contained objects, such as the CommerceItems or ShippingGroups, are loaded. Later, when an Order property is accessed (for example, by calling a method like getCommerceItems() or getShippingGroups() in the Order), the rest of the objects in the Order are loaded. See Refreshing Orders below for details. The atg.commerce.order.processor.ProcLoadOrderObject class implements this functionality. |
loadPriceInfoObjects
| Creates OrderPriceInfo and TaxPriceInfo objects for the given Order and loads their properties from the Order Repository. Note that only the OrderPriceInfo and TaxPriceInfo objects are loaded at this point. Later, when an Order property is accessed (for example, by calling getPriceInfo() or getCommerceItems() in the Order), the rest of the AmountInfo objects in the Order are loaded, such as the ItemPriceInfo objects in the CommerceItems and the ShippingPriceInfo objects in the ShippingGroups. See Refreshing Orders below for details. The atg.commerce.order.processor.ProcLoadPriceInfoObjects class implements this functionality. For more information about PriceInfo objects, see the Commerce Pricing Engines chapter. |
For more information about the OrderManager, see the Working With Purchase Process Objects chapter. For more information about pipelines, the PipelineManager, and the transactional modes and transitions of the processors in the loadOrder pipeline, see Appendix F, Pipeline Chains.
