[MGNLRES-118] Iteration over multiple loaders stops when a resource can't be loaded Created: 24/Jul/14  Updated: 29/Mar/22  Resolved: 27/Aug/14

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 1.5.11
Fix Version/s: 1.5.12, 2.2.7, 2.3.2

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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
Date of First Response:
Team: Nucleus

 Description   

In the case where multiple resource loaders are configured, if one of the resources can't be loaded due to an IOException then the whole process stops. It should be, that it tries the next loader that's configured and only fail when its tried all possibilities without success.


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