-
Improvement
-
Resolution: Obsolete
-
Neutral
-
5.4.4
-
None
-
-
Empty show more show less
-
Basel 31
-
1
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.
Acceptance criteria
- depends upon
-
MAGNOLIA-6515 Starting 5.4.4 on WebSphere server fails to start modules
- Closed
- is superseded by
-
MAGNOLIA-6523 Refactor ClasspathResourceOrigin and stabilise its hot resource modification support
- Closed
- mentioned in
-
Page Loading...