ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (Jira)" <j...@apache.org>
Subject [jira] [Updated] (OFBIZ-8297) Convert <property-to field functions to tenant-aware solutions
Date Sun, 02 Feb 2020 11:17:00 GMT

     [ https://issues.apache.org/jira/browse/OFBIZ-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pierre Smits updated OFBIZ-8297:
--------------------------------
    Description: 
*<property-to-field ...* functions look specifically to content in .property files when
it comes to retrieving runtime configuration variables. 

While this flawed approach is most prevalent when working with a multi-tenant setup, where
 default values of runtime configuration parameters can differ from tenant to tenant, it
is also a wrong approach when using OFBiz in controlled production setups. 
When an adopter is required to change the value of a  runtime configuration parameter, it
is required to go into a code upgrade process instead of changing the value through the admin
component (web tools).

  was:*<property-to-field* functions look specifically to content in .property files when
it comes to retrieving configuration variables. This doesn't work in a multi-tenant setup.



> Convert <property-to field functions to tenant-aware solutions
> --------------------------------------------------------------
>
>                 Key: OFBIZ-8297
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-8297
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Assignee: Michael Brohl
>            Priority: Minor
>         Attachments: OFBIZ-8297-AgreementScreens.xml.patch, OFBIZ-8297-AgreementScreens.xml.patch
>
>
> *<property-to-field ...* functions look specifically to content in .property files
when it comes to retrieving runtime configuration variables. 
> While this flawed approach is most prevalent when working with a multi-tenant setup,
where  default values of runtime configuration parameters can differ from tenant to tenant,
it is also a wrong approach when using OFBiz in controlled production setups. 
> When an adopter is required to change the value of a  runtime configuration parameter,
it is required to go into a code upgrade process instead of changing the value through the
admin component (web tools).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message