[MAGNOLIA-6490] NodeVisitor skips jcr:content nodes in DAM workspace Created: 08/Jan/16 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Nils Breunese | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I wanted to visit all nodes in the DAM workspace and figured I could do that like this in Groovy: Node damRoot = SessionUtil.getNode(DamConstants.WORKSPACE, '/') NodeUtil.visit(damRoot, new NodeVisitor() { @Override void visit(Node node) throws RepositoryException { // TODO: Do my business } }) To my surprise this visitor did not visit a mgnl:resource node that I knew existed in this workspace at a path like /folder/asset/jcr:content. The reason for this seems to be that NodeUtil.visit(Node node, NodeVisitor visitor) applies the info.magnolia.jcr.util.NodeUtil#EXCLUDE_META_DATA_FILTER predicate and this predicate makes sure that any node that has a name starting with NodeTypes.JCR_PREFIX (jcr:). However, as far as I know those jcr:content nodes are not meta data nodes (MetaData subnodes don't even exist in Magnolia 5 anymore). I feel that that jcr:content node should also have been visited by calling NodeUtil.visit. |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |