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/07/20 18:49:00 UTC
[jira] [Closed] (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 closed OFBIZ-11100.
----------------------------------
> 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
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11100_0001-Improved-Remove-support-for-ofbiz-containers.xml.patch, OFBIZ-11100_0002-Improved-Deprecate-ContainerConfig-getConfiguration-.patch, OFBIZ-11100_0003-Improved-Inline-filterContainersHavingMatchingLoader.patch, OFBIZ-11100_0004-Improved-Access-configurations-inside-loadContainers.patch, OFBIZ-11100_0005-Improved-Pass-directly-the-loaders-to-loadContainers.patch
>
>
> To extend the containers loaded on startup, it is possible define a
> container element either in the global “ofbiz-containers.xml” file or in
> the “ofbiz-component.xml” file from each 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 base
> container which is loading the components which is currently defined in
> this file.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)