[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461818#comment-17461818 ] Taher Alkhateeb commented on OFBIZ-6670: Hi jacques yeah ignore my comment. Funny thing I just corrected my comment two minutes after posting but it did not go through and I tried right now for 2 times and same happened. Something seems to be wrong in the mobile interface version of JIRA > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461815#comment-17461815 ] Jacques Le Roux commented on OFBIZ-6670: Hi Taher, I'm not sure why you speak about Java "system properties". The subject here is about SystemProperties OFBiz entity. Are you trying to make a parallel or is it just a confusion? > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[
https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458450#comment-17458450
]
Taher Alkhateeb commented on OFBIZ-6670:
Hello folks. I hope you're all doing well.
if you check the
[documentation|https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html]
of system properties you will notice that it's used for very high-level
environment configuration with things like "java.class.path" or "os.name" or
"path.separator".
You can say it's almost exclusive to making sure your software can run on a
specific machine or something like that. It's therefore _not_ designed to be a
part of your software solution and should be used very sparingly and only when
you _have_ to. Otherwise it should be really a database or properties file or
something like that.
Another quote from the above mentioned website "{*}Warning:{*} Changing system
properties is potentially dangerous and should be done with discretion. Many
system properties are not reread after start-up and are there for informational
purposes. Changing some properties may have unexpected side-effects."
I hope this is useful!
> Have configuration options for Content.
> ---
>
> Key: OFBIZ-6670
> URL: https://issues.apache.org/jira/browse/OFBIZ-6670
> Project: OFBiz
> Issue Type: Sub-task
> Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Fix For: Upcoming Branch
>
>
> The configuration of an OFBiz is determined by 2 aspects:
> # configuration settings required to successfully start the implementation
> # configuration settings required to have component functions work properly
> The latter involve default choices for various functions to cater to the
> usability of business processes (and therefore screen/forms and/or
> screens/templates.
> Several of these configuration settings are already loaded into the
> SystemProperty table in the underlying RDBMS, to enable adjustments of the
> systemPropertyValue while the implementation is in use. While it is not
> expected that these settings change often, it is possible that they are
> required to be changed during the lifespan of the company/organisation.
> However, it should not be required to go through a deployment process of
> regarding such changed configuration settings in the OFBiz production
> instance (which most - if not all - companies/organisations require when
> files are changes).
> Having all configuration settings of components in the SystemProperty table
> enhances the usability of OFBiz allowing system administrators to adjust the
> value(s) of system property records while the instance keeps running.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458394#comment-17458394 ] Michael Brohl commented on OFBIZ-6670: -- [~jleroux] I'm done with the discussion here and politely ask you to make your decision if you want this to stay in the codebase as-is or revert/rework. I would really appreciate if we could slow down a bit with merging all those changes to be able to do proper reviews. I fear that we else will have a lot of work to clean this up later. I would like to support this more, but cann not spare enough time at the moment. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458393#comment-17458393 ] Michael Brohl commented on OFBIZ-6670: -- If those examples are not of interest for you, you can just ignore them. The main points I am making are clear, I guess. I do not see what this issue has to do with code clean-up. In this state, it does not clean up but adds more confusion to the codebase. I'm trying to improve what you have started but you seem to see that as a personal attack. This makes collaboration unnecessary hard. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458387#comment-17458387 ] Pierre Smits commented on OFBIZ-6670: - So you don't have to bring up that 'Ecomify's Gradle based' approach here. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458386#comment-17458386 ] Pierre Smits commented on OFBIZ-6670: - The disinterest of the community to clean-up code (as with various other elements, like e.g. labels) is not a means to disparage improvements. What you have implemented downstream at your customers is the project's concern. Your 'Gradle based' approach? Is that the thing you referenced recently? And that you promised to write a page about? If not documented in the project (and/or explained in detail on a project's ml) it does not exist. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458381#comment-17458381 ] Michael Brohl commented on OFBIZ-6670: -- This is not correct. SystemProperty is designed to allow overriding the file based configuration properties at runtime. SystemProperty will also only work if the underlying code uses the EntityUtilProperties API instead of the UtilProperties API. AFAIK this is not the case for all properties, thousands use UtilProperties. It is also not reasonable to have runtime changes for certain properties, e.g. when the code fills constants with those properties. A change in the database would have no use later on. So it makes no sense to demand each configuration property to be in SystemProperty. The projects I know do not use SystemProperty at all or only in rare cases when a property has to be changed without restarting the instance. There are several other configuration mechanisms used in the field (see Nereide's environment variable based approach or ecomify's Gradle based approach). SystemProperty is a nightmare for devops because it is not transparent, needs additional sets of loading data for each target system and cannot be version controlled in the place where it's stored (the database). So, in my opinion, it is not reasonable to * put ALL available properties in SystemProperty * make this data load automatically I propose to have checked which properties make sense to be in the database, remove all others and remove it from any automatic loading mechanism. This way it is harmless and also provides a good dataset for users using the mechanism to chose from. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458363#comment-17458363 ] Pierre Smits commented on OFBIZ-6670: - Hi Jacques, I came across this one: OFBIZ-4730. Both the discussion and the ticket were catalysts to the change. However, though good suggestions were made in the thread, nobody picked up on the aspect of difference between the configuration aspects for OFBiz initialisation and the configuration aspects vis-a-vis runtime. Applications don't not need initialisation configuration as framework takes care of that. So, anything in an application's property file is to be considered as 'run-time'. And thus to be in a SystemProperty record. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458345#comment-17458345 ] Jacques Le Roux commented on OFBIZ-6670: PIerre, AFAIK, this is the 1st occurence about SystemProperty in dev ML: https://markmail.org/message/be3ts56b5w22k6pz I was working on the project that wanted multitenant put in in 2010. There were no SystemProperties then. I though agree that it makes runtime configurations easier. Unfortunately it also breaks things as we can see in OFBIZ-6189... It's a long time I would like OFBIZ-7112 properly discussed and closed. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458324#comment-17458324 ] Pierre Smits commented on OFBIZ-6670: - Hi Jacques, Aren't you mixing things up? Runtime configuration through SystemProperty records and OFBIZ-7112 are not just related to multi-tenancy. It is runtime related configuration, as opposed to initialisation related. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458311#comment-17458311 ] Jacques Le Roux commented on OFBIZ-6670: This is what I commented and forgot in OFBIZ-6189 bq. For me, this and other alike are waiting because of a pending collective decision on OFBIZ-7112 Still pending (indefinitely?). If people using multitenant can't use it we should better get rid of it. Like we did for the POS. Note that the webPOS is still not usable OOTB as was the POS :/ > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458192#comment-17458192 ] Michael Brohl commented on OFBIZ-6670: -- I do not see any reasons for joking here... Loading data in SystemProperty per default holds the risk that a user does not recognize it and gets confused with the configuration options. We had user requests/error reports in the past where this was the case (I remember someone who had problems sending emails). You may find that funny but it happens and can be avoided simply by not loading the SystemProperty data by default. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458179#comment-17458179 ] Pierre Smits commented on OFBIZ-6670: - [~mbrohl], If contributors fail to understand the reason d'être of SystemProperty records, then - IMO - a explanatory page in our Confluence could help. Maybe you can write one up? Secretly overrides values of records in the database? Wow! Does that happen? How would we tell? All joking aside, if that happens there is something bigger going wrong in the organisation using OFBiz. Nevertheless, with metadata fields createdByUserlogin and lastModifiedByUserlogin automatically populated for all entities (as per OFBIZ-12391) you would have more insights about who created and/or modified the records and when. As for 'in the past'; we had a lot not available in the past that we have now. Having data in OFBiz, but not having it in OFBiz is > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458174#comment-17458174 ] Jacques Le Roux commented on OFBIZ-6670: Hi Michael, So you would like to change from seed to demo, or? Also it would be good indeed Pierre if you could answer to Taher, TIA. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458061#comment-17458061 ] Michael Brohl commented on OFBIZ-6670: -- [~jleroux] Can we please try to clear open questions from other contributors towards those implementations? There already is an open question from [~taher] in this Jira which is not answered. Also, I think it is not a good idea to load this data as seed data. There is a danger that configured settings (through properties) are secretly overriden by this. In the past, we had very few default settings which are automatically loaded in the SystemProperty entity. > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-6670) Have configuration options for Content.
[ https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457961#comment-17457961 ] ASF subversion and git services commented on OFBIZ-6670: Commit 7b492abd8982a2b60e5f8adc8d0e88a4dce62082 in ofbiz-framework's branch refs/heads/trunk from Pierre Smits [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=7b492ab ] Improved: Have configuration options for Content (OFBIZ-6670) (#398) Improved: Have configuration options for Content (OFBIZ-6670) The configuration of an OFBiz is determined by 2 aspects: configuration settings required to successfully start the implementation configuration settings required to have component functions work properly The latter involve default choices for various functions to cater to the usability of business processes (and therefore screen/forms and/or screens/templates. Several of these configuration settings are already loaded into the SystemProperty table in the underlying RDBMS, to enable adjustments of the systemPropertyValue while the implementation is in use. While it is not expected that these settings change often, it is possible that they are required to be changed during the lifespan of the company/organisation. However, it should not be required to go through a deployment process of regarding such changed configuration settings in the OFBiz production instance (which most - if not all - companies/organisations require when files are changes). Having all configuration settings of components in the SystemProperty table enhances the usability of OFBiz allowing system administrators to adjust the value(s) of system property records while the instance keeps running. added: SystemProperty records in ContentSystemPropertyData.xml Modified: ofbiz-component.xml: reference of ContentSystemPropertyData.xml to load at seed loading moment added: missing SystemProperty records in ContentSystemPropertyData.xml Thanks to Jacques for the review > Have configuration options for Content. > --- > > Key: OFBIZ-6670 > URL: https://issues.apache.org/jira/browse/OFBIZ-6670 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > > The configuration of an OFBiz is determined by 2 aspects: > # configuration settings required to successfully start the implementation > # configuration settings required to have component functions work properly > The latter involve default choices for various functions to cater to the > usability of business processes (and therefore screen/forms and/or > screens/templates. > Several of these configuration settings are already loaded into the > SystemProperty table in the underlying RDBMS, to enable adjustments of the > systemPropertyValue while the implementation is in use. While it is not > expected that these settings change often, it is possible that they are > required to be changed during the lifespan of the company/organisation. > However, it should not be required to go through a deployment process of > regarding such changed configuration settings in the OFBiz production > instance (which most - if not all - companies/organisations require when > files are changes). > Having all configuration settings of components in the SystemProperty table > enhances the usability of OFBiz allowing system administrators to adjust the > value(s) of system property records while the instance keeps running. -- This message was sent by Atlassian Jira (v8.20.1#820001)
