[
https://issues.apache.org/jira/browse/OFBIZ-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042951#comment-17042951 ]
Pierre Smits commented on OFBIZ-8297:
-------------------------------------
I like this issue to get resolved, like any other issue, in an acceptable and amicable way that is beneficial to the project's adopters. And as is intended by The Apache Way.
But your comments, [~mbrohl], aren't helping. They are rather (together with your actions) obstructive towards that goal. Maybe you should recuse yourself?
> 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: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Michael Brohl
> Priority: Minor
> Labels: configuration
> 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)
Locked
