[
https://issues.apache.org/jira/browse/OFBIZ-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743206#action_12743206
]
Bob Morley commented on OFBIZ-2753:
-----------------------------------
Hi Scott,
Yes I think that would be true. In our current situation, we are not even
using the ecommerce application -- sales orders are placed face to face; but
may be taken over the phone or through a few different channels. In either
case, the requirement as that we would create the order up-front and allow
changes to it overtime before the customer was ready to "make payment". Our
approach was to save the order right at the beginning and with every change so
while we use the ShoppingCart, it is really just a transport vehicle (with
functionality) to get us to the order. This produced a number of issues around
editing orders, handling removed items, inventory reservation, etc.
If the editing process was changed to be more like the initial order entry
process I think it would simplify things for us. We would likely use this
behaviour with every gesture from the user, but we would know that when we
hydrate the shopping cart from the order in the database, make modifications,
and persist that things would be handled properly. Perhaps moving inventory
reservation to be tied to a status change on the order instead of the simple
creation of the order/order items. (Some of this is from memory).
Thoughts?
> Cart that is loaded from an order has its orderId set to null
> -------------------------------------------------------------
>
> Key: OFBIZ-2753
> URL: https://issues.apache.org/jira/browse/OFBIZ-2753
> Project: OFBiz
> Issue Type: Improvement
> Components: order
> Affects Versions: SVN trunk
> Reporter: Bob Morley
>
> ShoppingCartEvents.loadCartFromOrder has the following near the bottom of the
> method:
> // Since we only need the cart items, so set the order id as null
> cart.setOrderId(null);
> I believe this is ok with standard Ofbiz applications because the only time a
> shopping cart is loaded from an order i when you wish to initiate the order
> entry process from an existing order (you will be creating a new order). In
> our system however, you can start an order, persist it, and then pick it up
> later to make more adjustments. In this scenario the actual orderId should
> be available (and accurate) to the order that was used for loading.
> Recommendation - create a new service method "initializeCartFromOrder" or
> provide a parameter that indicates if the intent is to load into the cart for
> initialization (vs. for existing order manipulation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
