You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mathieu Lirzin (JIRA)" <ji...@apache.org> on 2019/06/10 15:40:00 UTC
[jira] [Updated] (OFBIZ-11100) Remove support for
"ofbiz-containers.xml"
[ https://issues.apache.org/jira/browse/OFBIZ-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mathieu Lirzin updated OFBIZ-11100:
-----------------------------------
Attachment: OFBIZ-11100_Remove-support-for-ofbiz-containers.xml.patch
> Remove support for "ofbiz-containers.xml"
> -----------------------------------------
>
> Key: OFBIZ-11100
> URL: https://issues.apache.org/jira/browse/OFBIZ-11100
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Mathieu Lirzin
> Assignee: Mathieu Lirzin
> Priority: Major
> Attachments: OFBIZ-11100_Remove-support-for-ofbiz-containers.xml.patch
>
>
> To extend the containers loaded on startup, it is possible to both
> edit the “ofbiz-containers.xml” file and alternatively define a
> container in a component.
> This redundancy adds extra complexity in the startup process for no
> good extensibility reason. The component container loader is more
> flexible since it allows developper to add new containers without
> touching the framework so it is better to only rely on this option.
> In order to simplify the startup process I am proposing to remove the "ofbiz-containers.xml" config file and hard-code the required component container which is defined in this file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)