WabBundleProcessor classpath scanning is extremely inefficient

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.0 CE GA1
• Fix Version/s: 7.0.0 DXP FP84, 7.0.10.12 DXP SP12, 7.0.X, 7.1.10 DXP FP13, 7.1.X, 7.2.10 DXP FP1, 7.2.X, Master
• Component/s: Core Infrastructure > Wab Extender
• Labels:
  • QA-TBD
  • ee-ts
  • liferay-fixpack-de-84-7010
  • liferay-fixpack-dxp-1-7210
  • liferay-fixpack-dxp-13-7110
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 1
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/75080
• Bug Type: Performance

The classpath scanning in com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor for ServletContainerInitializer support is extremely inefficient:

• A full classpath scan is performed even if the HandlesTypes annotation is absent or empty
• A full classpath scan is performed for each ServletContainerInitializer (instead of one scan for all)