[
https://issues.apache.org/jira/browse/OFBIZ-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296604#comment-15296604
]
Wai commented on OFBIZ-7112:
----------------------------
That's correct Jacques. My reasoning is that the database overrides the
properties file. Otherwise it wouldn't make sense.
Hence, if there is an entry in the database (even thought the assoc value is
empty) we should use the database. If the properties files are preferred, then
remove the entry from the database.
> EntityUtilProperties
> --------------------
>
> Key: OFBIZ-7112
> URL: https://issues.apache.org/jira/browse/OFBIZ-7112
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Wai
> Attachments: OFBIZ-7112.patch, OFBIZ-7112.patch
>
>
> Ofbiz reads properties from either a properties file or the
> entity:SystemProperty. The way it works previously is that ofbiz reads from
> the entity:SystemProperty first and if there is no value associated with the
> target propertyname, it would then locate the value from the relevant
> properties file.
> In other words, if there is a database entry for a property, the database
> entry should override the associated properties file.
> The issue is that if a database entry exist but the value is empty, it would
> look for a value from the properties file. It should not do so. If a
> database entry exists for the propertyname of interest, the value should be
> taken from the database even if it holds an empty value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
