[MGNLDATA-150] RegisterNodeTypeTask should also create root path Created: 14/Mar/12 Updated: 15/Mar/16 Resolved: 15/Mar/16 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Joerg von Frantzius | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Our module has declared a module-dependency on the categorization module, and so we were assuming that the "/categorization" root path does exist already in the data repository when our custom ModuleVersionHandler is executed. Unfortunately, for types registered with a RegisterNodeTypeTask, the rootpaths are created in the data repository only after versionhandlers have executed, namely during DataModule.start(). That's what the categorization module does. This is usually a problem only on first server startup with an empty repository, which still creates irritation with our client when they startup our first application delivery. Also it takes some time to find out what the problem is, since we had a proper dependency on categorization module. Would it be possible that RegisterNodeTypeTask also creates the necessary root path? DataModule.createRootPath() seems to be doing only: ContentUtil.createPath(hm, rootPath, new ItemType(DataConsts.FOLDER_ITEMTYPE));
If RegisterNodeTypeTask can get access to the type definition, it should be able to do the same? |
| Comments |
| Comment by Michael Mühlebach [ 15/Mar/16 ] |
|
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. |