* Implemented: Have a service that runs periodically to create CustomTimePeriod records
(OFBIZ-10905)
added: service createFuturePeriod
added: function createFuturePeriod called by createFuturePeriod
added: SystemProperty records called by createFuturePeriod function
added: JobSandbox record to schedule createFuturePeriod service
added: ref to CommonScheduledServicesDemoData.xml in component.xml
* Implemented: Have a service that runs periodically to create CustomTimePeriod records
(OFBIZ-10905)
improved: description
* Implemented: Have a service that runs periodically to create CustomTimePeriod records
(OFBIZ-10905)
improved: groovy code aligning to code formats
(OFBIZ-10282)
Thanks to Arun Patidar for reporting and review.
Thanks to Suraj Khurana for providing patch for the improvement.
Thanks to Jacques for discussion and finalizing the work.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1830545 13f79535-47bb-0310-9956-ffa450edef68
OFBiz reads properties from either a properties file or the entity:SystemProperty. The way it worked 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.
"isExistInDb" is first defined in Map<String, String> getSystemPropertyValue(String, String, Delegator). This method is call by many other methods. "isExistInDb" is used to indicate whether the method is returning an empty value for the property that 'exists' in the database rather than as a result of an absent database entry for the property.
The other methods...
boolean propertyValueEqualsIgnoreCase(String, String, String, Delegator)
String getPropertyValue(String, String, String, Delegator)
String getPropertyValue(String, String, Delegator)
String getMessage(String, String, Locale, Delegator)
uses the above method and needs to decide whether to use the empty value returned (ie. empty value from an existing property entry in database) or decide if it needs to read from the property file (ie. property entry does not exist in database)
jleroux: this also add systemPropertyValue data in CommonSystemPropertyData.xml
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1748560 13f79535-47bb-0310-9956-ffa450edef68
- by default leave the values in the entity null
- use findOne method to get SystemProperty by primary key
- add check whether system property's value empty before using properties file
This change to make sure current users of a non tenant installation are not affected.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1239451 13f79535-47bb-0310-9956-ffa450edef68