[DOCU-1690] How to get rid of JCR node types and workspaces Created: 13/Sep/18 Updated: 11/Nov/21 |
|
| Status: | Open |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | 6.0 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Epic Link: | Content types_1.x_official-release | ||||
| Description |
|
As a Magnolia developer I want to know how to "ged rid of" no more used workspaces and node types. So far we have https://documentation.magnolia-cms.com/display/DOCS60/How+to+delete+a+JCR+workspace But we need more. Explain what can be done & a bit of terminologyWhat can be done ...
... for both node types and workspaces. Provide proper recipes
*) remove is just a placeholder here. Once we have proper "terms" - we can give approproate titles. Or at least explaining: " ... to remove, you can unregister, then you can delete ..." ... or what not (This comes from https://wiki.magnolia-cms.com/display/TH2/CT+docs+feedback) Drawbacks and recommendationsI know that jackrabbit has some limitations - not implementing some of the JCR interface methods. What drawbacks a developer must keep in mind? |