[MAGNOLIA-6501] Expose event type from ClasspathScanner Created: 18/Jan/16  Updated: 22/Feb/16  Resolved: 01/Feb/16

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

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 5h
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2016-01-28 at 13.50.21.png    
Issue Links:
dependency
depends upon MAGNOLIA-6515 Starting 5.4.4 on WebSphere server fa... Closed
supersession
is superseded by MAGNOLIA-6523 Refactor ClasspathResourceOrigin and ... 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)
Date of First Response:
Epic Link: Resource reloading without restart
Sprint: Basel 31
Story Points: 1

 Description   

Current implementation of ClasspathScanner and ClasspathResourceOrigin, requires to openStream/connection for each modified resource. However, with introduction of event mechanism to ClasspathScanner and some other slight changes, we will not have to verify the deletion of a given resources due to events. Thus, we can get this information in the ClasspathScanner itself and pass it to ClasspathResourceOrigin.



 Comments   
Comment by Aleksandr Pchelintcev [ 28/Jan/16 ]

Clirr report:

To me this looks alright - the convoluted part of ClasspathScanner API is now split in parts, a protected method of ClasspathResource has been removed, but that method was sort of a hack anyway.

Comment by Michael Mühlebach [ 01/Feb/16 ]

This issue should be solved by MAGNOLIA-6523.

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