Fix threadlocal usage in util-taglib

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.X, 7.1.X, 7.2.10 DXP FP2, 7.2.10.1 DXP SP1, 7.2.X, Master
• Component/s: Core Infrastructure, Frontend Infrastructure > UI Taglibs
• Labels:
  • liferay-dxp-72-sp1
  • liferay-fixpack-dxp-2-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/77959

Util-taglib is a special jar which is loaded twice, once by portal classloader, another one is as osgi module. As a result, the threadlocal enclosing class is definited twice. When we consume the threadlocal values from both portal classloader scope and module classloader scope, they are actually different. To fix it, we use ThreadLocalUtil to force module version threadlocal to get portal version's threadlocal object reference, so although the class is defined twice, we only have one threadlocal object.