Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7014

MagnoliaServletContextListener and MagnoliaInitPaths don't play well together

    Details

    • Type: Bug
    • Status: Open
    • Priority: Neutral
    • Resolution: Unresolved
    • Affects Version/s: 5.5.3
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Testcase included:
      Yes

      Description

      The MagnoliaServletContextListener gets the server name from MagnoliaInitPaths and makes it available as a server property.
      The module registration happens afterwards.

      This has the following side effects:

      • The values provided by MagnoliaInitPaths cannot be properly overridden as it depends on module registration when this will be available.
      • Modules cannot grant that they will access proper values in MagnoliaInitPaths as it's not sure that the module providing the override had already been started.
      • The system property server that will be set is inherently unreliable in these cases.

      The issue can be checked out in the following GIT Repository:

      Possible solutions:

      • Do NOT make this customizable, so the values might be provided by the web.xml itself.
      • Improve the implementation of the default DefaultMagnoliaInitPaths so it allows to use properties as a primary source for it's values.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              costamojan Daniel Kasmeroglu
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: