[
https://issues.apache.org/jira/browse/OFBIZ-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858562#action_12858562
]
Bob Morley commented on OFBIZ-3646:
-----------------------------------
I guess I would think that there is no potential mistake here. As the
application developer you likely always want to fetch from cache (if you are
not updating); if that item will never be from the cache (because it is
non-cachable) or if the entity just happens not to be in the cache for that
request, there isn't much difference. I would not expect the application
developer to look at each entity and set the "cache query" appropriately, only
to have the underlying entity change and be forced to find all of those queries
and change them to be cachable.
> Change log level on never-cache related messages from "warn" to "info"
> ----------------------------------------------------------------------
>
> Key: OFBIZ-3646
> URL: https://issues.apache.org/jira/browse/OFBIZ-3646
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Bob Morley
> Fix For: SVN trunk
>
> Attachments: OFBIZ-3646_ChangeLogLevelForNeverCacheMessages.patch
>
>
> When you use caching there are a number of warning messages that are produced
> indicating that various entity instances will not be cached (because the
> entity is configured not to cache). Changing these from "warn" to "info"
> which better reflects what they are and reduces warn threshold log noise.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
