Introduce uniform resource loading API (MAGNOLIA-6128)

[MAGNOLIA-6126] FileResourceLoader vs Origin consistency and cleanup Created: 12/Mar/15  Updated: 08/May/15  Resolved: 06/May/15

Status: Closed
Project: Magnolia
Component/s: configuration
Affects Version/s: None
Fix Version/s: 5.4

Type: Sub-task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6124 Origin interface improvements Closed
Template:
Sprint: 5.4 Sprint 4

 Description   

Since order matters - consider instantiating origin instead of injecting them, or use the Builder pattern to be able to explicitly specify the order, have other sets of Origins.
If we use Builders, we should then also specify pathPattern there, and remove the #start(Pattern) method from the interface.
As a side note, FileResourceLoader could actually also be an Origin, we could well merge the two interfaces.


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