[MAGNOLIA-6244] Restore "relayer" function in LayeredOrigin when notifying of resource changes Created: 04/Jun/15  Updated: 07/Jun/15  Resolved: 05/Jun/15

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

Type: Bug Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: config, resources
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-6130 Revisit use case and approach for obs... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Currently passes non-layered ResourcePath, as is, back to the config source's ResourceVisitor, hence ignoring LayeredOrigin's loading cascade for config reloads.

Needs test as well.



 Comments   
Comment by Mikaël Geljić [ 04/Jun/15 ]

Linking to MAGNOLIA-6130 as 'related', doesn't prevent the scanning functionality from working as such.

Comment by Mikaël Geljić [ 05/Jun/15 ]

3 sparse commits on branch feature/MAGNOLIA-6130-classpathwatch

  • Introduced RelayerResourceVisitor, in the spirit of the old RelayerFunction (was unused, now deleted).
Generated at Mon Feb 12 04:12:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.