[MAGNOLIA-6524] Origins should log events around Resources Created: 01/Feb/16  Updated: 07/Jul/17  Resolved: 07/Jul/17

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

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-6523 Refactor ClasspathResourceOrigin and ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Resource reloading without restart
Story Points: 13

 Description   

As a developer and admin I want to see operations around resources in the logs to see if their changes, especially to the classpath and filesystem, are picked up.

Acceptance criteria

  • It should be logged if resources are changed and reloaded
  • It should be logged if resources are deleted and unloaded
  • It should be logged if resources are added and loaded
  • Depending the API is delivering there informations


 Comments   
Comment by Michael Mühlebach [ 16/Mar/17 ]

We log modifications on the level of the registry.
How does the logging described in this ticket differentiate to the one on the registry?
How can we prevent duplications?

Comment by Mikaël Geljić [ 04/May/17 ]

@czimmermann What is the concrete scenario where you have reloading problems?
As far as I see, log messages—or lack thereof when resources don't reload—will be of little help in those cases.

Maybe we can do more with magnolia.develop, be it Vaadin production mode, resource cache time, browser cache policies or what have we.

Generally, resource changes happen under the hood (via servlet-container or IDE hot-swaps)—i.e. without having magnolia be aware of anything.

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