[MGNLCT-123] JCR registrations based on CT definitions should be executed during module start-up-phase Created: 20/May/19 Updated: 22/Nov/19 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | 1.0, 1.1 |
| Fix Version/s: | None |
| Type: | Task | 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
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Description |
|
JCR workspaces, name-spaces and node-types defined in datasources of content type definitions (CTs) are not properly initialized / registered during the start-up phase of the module which contains the CTs. Example / use case
The dependencies as shown in 3.1 probably are a bit "too much".
|