You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Pierre Smits (Jira)" <ji...@apache.org> on 2020/05/04 19:00:00 UTC

[jira] [Updated] (OFBIZ-6110) Move as much as possible demo data from ecommerce to product or order components

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

Pierre Smits updated OFBIZ-6110:
--------------------------------
    Component/s: party
                 marketing
                 accounting

> Move as much as possible demo data from ecommerce to product or order components
> --------------------------------------------------------------------------------
>
>                 Key: OFBIZ-6110
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6110
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: accounting, ecommerce, marketing, order, party, product
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Priority: Minor
>
> It would be better if we have most of the demo product data in product or maybe in order component. Because almost all what can be done concerning ordering in ecommerce can also be done in order manager from which anyway ecommerce depends on
> More generally each component should have the data to be able to work as much on its own as possible. Even if that means redundancy of some sorts. Most of the time, we can avoid redudancy when there are components dependencies and the component data are loaded after the main one.
> This is when https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies helps and shows why it should be actively maintained! For instance I'm not sure we show data loading order there...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)