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

Create OSGi config to serve as feature flag for "Remote Web Application" widget functionality


    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Discarded
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:


      As described in the research document, under "Backend needs → Functional requirements → High-level", the Remote Web Application feature will require a significant set of functionality to be integrated into master, so we want a feature flag that will allow us to ship it incrementally as pieces are completed:


      We're going to need:

      • Ability to create a config file, likely named something like "com.liferay.remote.web.apps.internal.configuration.RemoteWebAppsConfiguration.config".
      • Based on contents of file (either: enabled="true" or enabled="false"), once dropped into the DXP instance's "osgi/configs" directory, code can check at runtime to see whether Remote Web Applications functionality should be enabled.

      Note about the naming: want input on what the OSGi module itself should be called, as well as what Brian is likely to accept/reject (for example, if the widget lives in "remote-web-apps/remote-web-apps-web", will he object to the repetition of "web"?). The decision on naming will obviously also be relevant to LPS-116361, which is the task for creating the OSGi module in the first place.

      Note about granularity: at present, we're just proposing a single feature flag to cover access to the Remote Web Applications feature as a whole. At a later point if we realize we need more granular control, we can look at adding separate flags.




            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:


                Version Package