[MAGNOLIA-6128] Introduce uniform resource loading API Created: 16/Mar/15  Updated: 15/Sep/15  Resolved: 06/May/15

Status: Closed
Project: Magnolia
Component/s: resource-loader
Affects Version/s: None
Fix Version/s: 5.4

Type: Story Priority: Neutral
Reporter: Michael Mühlebach Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLINTEMPL-77 Migrate installed templates to the 'r... Closed
relates to MAGNOLIA-6266 Rename Origin and ResourcePath interf... Closed
relates to MAGNOLIA-6219 ClasspathOrigin: filter resources out... Closed
causality
is causing MAGNOLIA-6255 Resource loader fails at startup when... Closed
is causing MGNLRES-179 Migrate all resources from templates ... Closed
is causing MULTISITE-44 Review default bypasses for CrossSite... Open
dependency
is depended upon by MAGNOLIA-6233 Load module descriptors through resou... Closed
is depended upon by MAGNOLIA-6234 TranslationService could use new Reso... Closed
duplicate
is duplicated by MAGNOLIA-6175 magnolia.properties property to speci... Closed
supersession
supersedes MAGNOLIA-6106 The yaml configuration source is deco... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-6123 Use specific type to pass resource pa... Sub-task Closed Magnolia International  
MAGNOLIA-6124 Origin interface improvements Sub-task Closed Magnolia International  
MAGNOLIA-6126 FileResourceLoader vs Origin consiste... Sub-task Closed Magnolia International  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: 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


 Comments   
Comment by Magnolia International [ 30/Mar/15 ]

Work in progress under the feature/MAGNOLIA-6128-TypedResourcePath branch

Generated at Mon Feb 12 04:11:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.