[MAGNOLIA-2824] Magnolia Provider is missing API to unregister the Node types Created: 29/Jul/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File patch.txt    
Issue Links:
dependency
is depended upon by MGNLDATA-30 When deleting a type its custom nodet... Closed
Template:
Patch included:
Yes
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   

Currently Provider interface and its only implementation ProviderImpl class have an API to register custom node types, but not to unregister them.



 Comments   
Comment by Jan Haderka [ 29/Jul/09 ]

if you delete the type, it is not deregistered, so creating type with same name later again will fail

Comment by Jan Haderka [ 29/Jul/09 ]

Unfortunately, it seems this functionality itself is not currently implemented in JackRabbit ... see https://issues.apache.org/jira/browse/JCR-322 for details.

Comment by Jan Haderka [ 30/Jul/09 ]

Attached patch extending the API and providing the implementation of the method, but untill related JR issue is fixed there is little point in applying the patch in Magnolia.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:40:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.