Customizing the Pipeline definition files - XML Modifications

Adding the ApproveOrder pipelinelink to the existing pipeine chain.

<pipelinechain name="executeValidateForCheckoutChain ">     
     <pipelinelink name="ExecuteValidateForCheckoutChain"
               transaction="TX_MANDATORY" xml-combine="replace">
          <processor jndi="/atg/commerce/order/processor/

                                ExecuteValidateForCheckoutChain"/>
            <transition returnvalue="1" link="ApproveOrder"/>   

      </pipelinelink>
      
<pipelinelink name="ApproveOrder" transaction="TX_MANDATORY">
            <processor

            jndi="/atg/commerce/order/processor/ApproveOrder"/>
            <transition returnvalue="1" link="approverEmailIds"/>
       </pipelinelink>


Adding the processor Approve Order to the Pipeline Registry.

</pipeline-registry-configuration>
     ...........
  <processor-registry xml-combine="append-without-matching">
     <processor>
        <nucleus-

        path>/atg/commerce/order/processor/ApproveOrder</nucleus-
        path>
      <display-name>give a name ....</display-name>
      <category>Approve</category>
      <description>give a description</description>
    </processor>
  </processor-registry>

</pipeline-registry-configuration>

See the Java and Property files changes for a Component

2 comments:

Logeswar Madurainayagam said...

What are the different transaction modes and why are they used ? For eg : transaction="TX_MANDATORY"

Sebastian said...

you can refer atg oracle documentation for this http://docs.oracle.com/cd/E26180_01/Platform.94/ATGProgGuide/html/s1205transactionmodes01.html

Generally a transaction mode mandatory is used when the section of code is a part of a larger transaction and in that it verifies a transaction is already in place.

Post a Comment

Related Posts Plugin for WordPress, Blogger...