Uploaded image for project: 'Magnolia Data Module (closed)'
  1. Magnolia Data Module (closed)
  2. MGNLDATA-265

Installing data module's company sample on java 8 gives corrupted subapps order

    XMLWordPrintable

Details

    • Bug
    • Resolution: Outdated
    • Neutral
    • None
    • 2.3.2

    Description

      1. Given that bootstrap files for the company-app sample are split "per subapp";
      i.e. under src/main/resources/mgnl-bootstrap-samples/data we have the browser subapp + the 6 detail subapps at the same level as follows:

      • config.modules.data.apps.companyApp.subApps.browser.xml
      • config.modules.data.apps.companyApp.subApps.company.xml
      • config.modules.data.apps.companyApp.subApps.department.xml
      • config.modules.data.apps.companyApp.subApps.developer.xml ... and so on.

      2. Given that JCR bootstrap files are not guaranteed to be processed in any particular order.

      3. And given that the default subapp in apps when clicking the tile in the applauncher is always the first one — regardless of type or name;

      => When installing Magnolia on Java 8, the order bootstraps files are processed is different from Java 6, and thus the company detail subapp ends up being the first one.

      Consequently, opening the app from the applauncher opens an empty detail subapp, rather than the browser subapp.

      We may equally add an extra install task to order the browser subapp first, or aggregate all sample bootstraps into one.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              mgeljic Mikaël Geljić
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: