[
https://issues.apache.org/jira/browse/OFBIZ-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045248#comment-17045248 ]
Pierre Smits commented on OFBIZ-8297:
-------------------------------------
The minilang element <xs:element name="property-to-field" substitutionGroup="AllActions"> as used in screen definitions like EditAgreementItem uses the java class 'PropertyToField'.
This java class applies the 'EntityUtilProperties' function to retrieve the appropriate data from the SystemProperties entity (and if not available there, from the appropriate .properties file.
Will close with resolution 'Not an issue'.
> 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: Pierre Smits
> 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
