[
https://issues.apache.org/jira/browse/OFBIZ-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099897#comment-17099897
]
ASF subversion and git services commented on OFBIZ-6110:
--------------------------------------------------------
Commit bd50c1417b999c83d66494a566bfc4814a23c467 in ofbiz-plugins's branch
refs/heads/trunk from Pierre Smits
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=bd50c14 ]
Improved: move demo data from optional plugin to base application
(OFBIZ-6110)
removed: marketing component related data in ecommerce plugin
removed: reference to marketing demo data in component.xml of ecommerce plugin
> 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
> Assignee: Pierre Smits
> 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)
