Initialization bug when deploying modules with MBDisplayContextFactory or WikiDisplayContextFactory

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP10, 7.0.0 DXP SP2, 7.0.3 CE GA4, 7.1.X, Master
• Component/s: Collaboration, Message Boards, Wiki
• Labels:
  • QA-CT
  • liferay-digital-enterprise-70-sp2
  • liferay-fixpack-de-10-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/45766
• QA Test Name:
  • dont-test-again

There's an issue in the way the MBDisplayContextFactory and WikiDisplayContextFactory are registered that creates an issue when deploying new modules with those components in a specific order.

The classes MBDisplayContextProvider and WikiDisplayContextProvider are not properly registering the components *DisplayContextFactory. They are using ServiceReference instead of the entity and that forces to have the _bundleContext bind, but it might not have been initialized because the references are satisfied before the activate method.

Then, if there are pending *DisplayContextFactory before the *DisplayContextProvider is activated, the reference methods like setWikiDisplayContextFactory won't have the _bundleContext wired and it will fail when adding it to the map.

The fix is to replace the map with a List and use the entity instead of the service reference so we no longer need the bundleContext.