Details
-
Bug
-
Resolution: Won't Fix
-
Neutral
-
None
-
3.0
-
None
-
None
Description
Context - Displaying the origin of the resource
In the resources app, a resource's origin can be:
- File system
- Java classpath
- JCR
(1), (2) are frequently occurring.
(3) is a result of: edit resource (a hotfix of a resource originating from file or classpath), add resource, upload file or add folder.
The issue appears after deleting JCR based resources.
Reproducing the issue(s)
Example scenario - part 1
- Have a light-module foobar-module (on the file system)
- In the resources app:
- Add the folder static
- within static, upload a file lala.pngs and Add a file solala.yaml
- repeat the 2 steps above within mtk
The new resource(s) static/, static/lala.png and static/solala.yaml are all marked as origin from JCR.
That's correct.
Also the parent folders fobbar, mtk are marked as origin from JCR ... which is arguable .. but "understandable".
Example scenario - part 2
Now delete the created resources (/static/*) from above. (Currently you need the JCR app for this, see MGNLRES-341.)
In consequence, the resource should be "back to normal", showing the same origin as they had showed at the very beginning of the scenario. For instance,
- /foobar-module should show the "File system" origin
- /mtk should show the "Java classpath" origin
However ... both these folders still "claim" (show) to be of "JCR" origin, which is wrong.
Checklists
Attachments
Issue Links
- mentioned in
-
Page Loading...