Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

JavaScript Loader OSGI config settings don't appear to be applied following an upgrade to 7.2+

Written By

Isaac Wilson

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When upgrading to DXP 7.3, we moved our previously modified OSGi .config files to the new bundle, but the settings from the JavaScript Loader .config file do not appear to be taking effect, as the default values look to be in use.

Environment

  • Pre-upgrade environment: DXP 7.0 or DXP 7.1
  • Post-upgrade environment: DXP 7.2+

Resolution

  • Between 7.1 and 7.2, the naming convention used for the OSGi .config file was modified, from

    com.liferay.frontend.js.loader.modules.extender.internal.Details.config to com.liferay.frontend.js.loader.modules.extender.internal.configuration.Details.config

  • As such, renaming the *.internal.Details.config file to instead be com.liferay.frontend.js.loader.modules.extender.internal.configuration.Details.configwill allow the bundle to recognize and apply the JavaScript Loader settings as expected

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?