[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: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Resource reloading without restart | ||||||||
| Story Points: | 13 | ||||||||
| Description |
| Comments |
| Comment by Michael Mühlebach [ 16/Mar/17 ] |
|
We log modifications on the level of the registry. |
| Comment by Mikaël Geljić [ 04/May/17 ] |
|
@czimmermann What is the concrete scenario where you have reloading problems? 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. |