[
https://issues.apache.org/jira/browse/OFBIZ-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258051#comment-14258051
]
Scott Gray commented on OFBIZ-5930:
-----------------------------------
Since you've already done the work, I think this approach is fine as a stop-gap
measure. But we definitely need to come up with a better approach for caching
data coming from different delegators (multi-tenant or otherwise). There are
numerous places in OFBiz where database derived objects are cached and will
have this same problem.
I'll keep thinking about this while I work on the ehcache integration.
Thoughts from others would be most welcome!
> Data resouce caching issue while render data resource on multi tenant
> environment
> ----------------------------------------------------------------------------------
>
> Key: OFBIZ-5930
> URL: https://issues.apache.org/jira/browse/OFBIZ-5930
> Project: OFBiz
> Issue Type: Bug
> Components: content
> Affects Versions: Trunk
> Reporter: Deepak Dixit
> Attachments: OFBIZ-5930.patch
>
>
> Need to fix the DataResouce caching issue while render the DataResouce on
> multi tenant environment.
> It might be possible that same data resource id exists for multiple tenant,
> and as DataResouce caching does not used tenant specific caching so it may
> lead to incorrect data rendering.
> Here is the current code to get the DataResource Teamplate from cache
> {code}
> Template cachedTemplate = FreeMarkerWorker.getTemplate("DataResource:" +
> dataResourceId);
> {code}
> Need to add the delegator name as prefix to fix the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
