[MAGNOLIA-6712] Light module dependency check and decoration ordering should happen at runtime Created: 06/Jul/16  Updated: 19/May/22  Resolved: 19/May/22

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

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
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)
Date of First Response:

 Description   

Currently the module descriptor for light modules is only evaluated at system startup, which is consistant with maven modules. This means that check for dependencies, and the ordering of the decorators is only set at system startup.

A key value of light modules is that they take effect as soon as they are added to a running instance. This should also apply to the mechanisms tied to the module descriptor.
(It's correct that the module descriptor is also evaluated at system startup.)

When a light module is detected on a running instance:

  • If the module depends on some module/version that is not present, an error should be logged and a pulse message sent. (to users with superuser role?)
  • The application order of the decorators should be re-evaluated based on the dependencies and definitions reloaded if necessary.

When a light module is removed from a running instance:

  • The application order of the decorators should be re-evaluated based on the dependencies and definitions reloaded if necessary.


 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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