-
Bug
-
Resolution: Outdated
-
Neutral
-
None
-
5.4.5
Classpath service/origin should serve resource files no matter what; and regardless of how we model that as a virtual directory structure.
Assuming you have:
- in module A: src/main/resources/test/samename (plain text)
- in module B: src/main/resources/test/samename/subfile.txt (samename is now a virtual directory)
http://localhost:8080/magnoliaAuthor/.resources/test/samename is served properly
http://localhost:8080/magnoliaAuthor/.resources/test/samename/subfile.txt results in a 404
This is clearly highlighted in ClasspathEntryResolver, that it ignores sub-directory structures in such cases—which to me is just wrong.
Other potential harmful (and deferred) side-effect: create a "travel-demo" mgnl:content node in resources workspace, on next restart the whole travel-demo is down.
Defs are expectedly not registered; no static resource reachable in there either.
- caused by
-
MAGNOLIA-6523 Refactor ClasspathResourceOrigin and stabilise its hot resource modification support
- Closed
- relates to
-
MAGNOLIA-6433 Resouces in filesystem and classpath can be changed without restarting magnolia to improve experience for developers.
- Closed
-
MAGNOLIA-6376 ClasspathResourceOrigin should warn users about duplicate resources
- Open
- supersedes
-
MAGNOLIA-6575 ClasspathResourceOrigin doesn't reliably show children
- Closed
-
MAGNOLIA-6440 Duplicated resources on classpath may prevent magnolia from start with a NPE
- Closed