That will work if you change the variable name corresponding_po_id to correspondingPoId in the templates. We then need to double check that corresponding_po_id isn't used/expected elsewhere.
The placement of setPoNumber in the chain needs to be looked at as well. --- Jacopo Cappellato <[EMAIL PROTECTED]> wrote: > Before doing this, I think that it would worth trying to chain, in > the > checkout events in the ecommerce's controller the call to setPoNumber > > <request-map uri="setPoNumber"> > <security https="true" auth="true"/> > <event type="java" > path="org.ofbiz.order.shoppingcart.ShoppingCartEvents" > invoke="setPoNumber"/> > <response name="success" type="request" value="orderentry"/> > <response name="error" type="request" value="orderentry"/> > </request-map> > > it should work > > Jacopo > > Chris Howe wrote: > > Could someone please revert the changes made in rev 519570. This > > breaks the storing of a customer provided PO number in ecommerce. > > Thanks. > > > > ,Chris > >
