A warning at module level may or may not be warning at app level.
One can set log levels hierarchically. So you can set 'org.ofbiz.entity' to be logged at warning or higher and org.ofbiz.entity.cache or org.ofbiz.entity.cache.AbstractEntityConditionCache at error level.
Harmeet On 05/04/10 9:36 PM, Bob Morley wrote:
AbstractEntityConditionCache currently has a warning log message when the put method is called for an entity that has "never-cache" set to true. These messages literally flood our ofbiz log files on our servers because it is our standard practice to make heavy use of the application caching in Ofbiz. Would anyone have issue with changing this from a warning to an info message? My line of thinking here, is it is good for people to make entity calls with cache set to true and they should not have to consider the current configuration of the entity. If the entity happens to turn off caching, then an info message saying it had done so is probably sufficient. There are other similar messages such as storing by primary key that I would change from warning -> info as well. Internally we preferred this approach over configuration in log4j. The javadoc from log4j defined WARN as "The WARN level designates potentially harmful situations." and it does not seem to me that in this scenario that is true. Thoughts?
