[
https://issues.apache.org/jira/browse/OFBIZ-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025971#comment-17025971 ]
James Yong commented on OFBIZ-11296:
------------------------------------
I see the following benefits with using depends-on over component-load.xml:
(1) Know which components are non-dependents or redundant, and can be disabled.
(2) Clearer rules so that dependency isn't introduced unwittingly to the java code.
(3) Allow components to be dropped in without configuring the component-load.xml file.
(4) Better approach when we need to manage hundreds of components.
Some questions:
It is unknown how point (1) can be achieved with the removal of component-load.xml, but [~mbrohl] has mentioned component-load.xml being used to enable / disable the components to be loaded.
Another point raised is to control the ordering of components.
Understand there is a “commonext” component which is meant to be loaded last.
> Use 'depends-on' everywhere
> ---------------------------
>
> Key: OFBIZ-11296
> URL:
https://issues.apache.org/jira/browse/OFBIZ-11296> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Mathieu Lirzin
> Assignee: Mathieu Lirzin
> Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11296_0001-Improved-Use-depends-on-attribute-instead-of-compone.patch, OFBIZ-11296_ignore-depends-on-when-a-component-load.xml-is-prese.patch
>
>
> We currently have two ways to define component loading order. Either
> by using ‘depends-on’ attribute in “component-config.xml” or by adding
> a “component-load.xml” file at the root of a component directory.
> “depends-on” is more flexible because it handles partial ordering when
> “component-load.xml” defines a total order which is not necessarily
> meaningful, so it is better to rely only “depends-on”.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
