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

Introduce uniform resource loading API

    XMLWordPrintable

Details

    • Story
    • Resolution: Fixed
    • Neutral
    • 5.4
    • None
    • resource-loader
    • None
    • 5.4 Sprint 4

    Description

      A universal way of resource location has to be introduced - currently configuration, inplace-templating, Groovy, resources modules do that in a different way, we need to come with a reasonable common strategy and make those modules follow it.

      Traverse web-app, classpath, JCR workspace and filters relevant files

      Criterias

      • All resources for either web-page, groovy, configuration or modules can be loaded over one layer.
      • The resource loader provide a filtering mechanism to get just the relevant resources
      • The loader should cascade through all origins if it can not be provided by one origin
      • The order of loading should be:
        1. JCR
        2. Filesystem
        3. Classpath

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            There are no Sub-Tasks for this issue.

            Activity

              People

                gjoseph Magnolia International
                mmuehlebach Michael Mühlebach
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD