Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-68563

SoyPortlet expects an available package.json

    Details

    • Fix Priority:
      2

      Description

      In order for the UI to work on JS too, a controller must be loaded and instantiated.

      Since the controller's module will be defined as package-name/module-path and the package name comes from the package.json file, the SoyPortlet bridge requires it to know how to create the script to be placed in the page.

      At this line in SoyPortletHelper it is accessed and deserialized. The path where the helper expects it is in the root, as if it was src/main/resources/package.json.

      That's not the case because the package.json file, required for example by Liferay Loader Config Generator, must be in the root of the project (sibling to src itself).

      Currently a duplicate package.json must be placed in src/main/resources/ for SoyPortlets to work.

        Attachments

          Activity

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since last comment:
                3 years, 6 weeks, 2 days ago

                Packages

                Version Package