Introduce uniform resource loading API (MAGNOLIA-6128)

[MAGNOLIA-6123] Use specific type to pass resource path information around 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:
relation
is related to MAGNOLIA-6124 Origin interface improvements Closed
Template:
Date of First Response:
Sprint: 5.4 Sprint 4

 Description   

Ditch java.nio.Path usage, but don't replace it with String - use some custom type instead.
Could be an opaque wrapper around String for starters, but should aim to eliminate confusion regarding what kind of path we're dealing with (abs/relative/...?).



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

That interface could potentially have the openStream/openReader methods (in which each Origin will have its own impl) and exposes some other properties.
And/or it could be used as that one attribute we're still missing in the DefinitionMetadata that reflects the source/origin/path of the definition in use.
Location might be a decent name.

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