You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Nicolas Malin (Jira)" <ji...@apache.org> on 2021/09/29 14:07:00 UTC
[jira] [Created] (OFBIZ-12331) Improve velocity of
PartyHelper.getPartyName() with the cache
Nicolas Malin created OFBIZ-12331:
-------------------------------------
Summary: Improve velocity of PartyHelper.getPartyName() with the cache
Key: OFBIZ-12331
URL: https://issues.apache.org/jira/browse/OFBIZ-12331
Project: OFBiz
Issue Type: Improvement
Components: party
Affects Versions: Trunk, Release Branch 18.12
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Attachments: OFBIZ-12331.patch
The class PartyHelper is massively used to resolve the name of a party without know is type.
{code:java}
<field name="organizationPartyId" title="${uiLabelMap.ProductOrganization}">
<display description="${groovy: org.apache.ofbiz.party.party.PartyHelper.getPartyName(delegator, organizationPartyId, true);} [${organizationPartyId}]"/>
</field>
{code}
A party name have few change over time, or the PartyHelper.getPartyName function call the database at each call.
On huge screen, we distinctly clearly the database latency.
So for a cold data, no reason to use the cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)