[jira] Updated: (OFBIZ-659) Refactoring Create Order process

["Mridul Pathak (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Pathak updated OFBIZ-659:
--------------------------------

    Attachment: OrderChekoutProcess.patch

Anil and All
    I am working on the refactoring of Order Checkout Process in the Ordermgr for creating 2 different sets of request-map definitions and two different "progress bars", one for sales orders and one for purchase orders as par the description given in this issue.
    Here is the first patch from my side.
    The refactoring is not complete yet.  This is just a starting patch.  Here is some info of modifications or additions done in this new patch.
1)  Created two different paths for Sales Order and Purchase Order on the application menu.
2)  Only Sales Order Path is functional and not the Purchase Order path.
3)  Implemented initializeSalesOrder and setOrderCurrencyAgreementShipDates simple methods instead of using Java.
4)  Implemented screens to initialize sales order and purchase order.
5)  Added new request definitions.
    The Sales Order checkout process is functional and can be tested.  It doesn't affect the current Checkout Process except a small change in "additem" request-map, which will be removed when I'll submit the next updated patch.
    Right now I am wroking to split the ShowCart section for Sales and Purchase Order.  I'll Submit the updated patch as soon as I finish it.

> Refactoring Create Order process
> --------------------------------
>
>                 Key: OFBIZ-659
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-659
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: order
>            Reporter: Anil K Patel
>            Assignee: Anil K Patel
>         Attachments: OrderCheckoutProcess.patch, OrderCheckoutProcess.patch, OrderCheckoutProcess.patch, OrderCheckoutProcess.patch, OrderChekoutProcess.patch, OrderChekOutProcessRefac.patch, OrderChekOutProcessRefac.patch, OrderChekOutProcessRefac.patch, OrderChekOutProcessRefac.patch, OrderProcessSimpleMethods.patch
>
>
> Focus of this Jira Issue is Refactoring  Create Order Process, Implement a parallel code as needed so that the current Code remains intact.
> From David's email on Mailing list.
> Just some quick thoughts...
> Following the pattern of the anonymous and other checkout processes
> in the ecommerce app would be a great way to go.
> In the order manager there are various paths through the checkout
> process so we might have, for example, 2 different sets of request-
> map definitions and two different "progress bars", one for sales
> orders and one for purchase orders. These two different sets of high-
> level artifacts can point to the same views, services/events,
> screens, data prep scripts, etc wherever the two processes overlap.
> -David
> My Initial comments
> The anonymous checkout process in Ecommerce component provides some high level guiding principals. Few things that I can think of are
> 1) moving some code that's embedded in Java classes into small simple methods.
> 2) Moving process control logic from event handlers to Controller file. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.