[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:
relation
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

  1. Have a custom module which contains some CTs defining JCR workspaces, namespaces and node-types
  2. Have another custom module containing bootstrap data for the workspaces which are defined in (1).
  3. Define dependencies accordingly 
    1. Module-1 depends on content-types and ui-framework-core
    2. Module-2 depends on content-types , ui-framework-core and module-1.

The dependencies as shown in 3.1 probably are a bit "too much".
I (hopefully) should be sufficient to define only the dependency between the 2 custom modules.
However, I have defined it as shown above in my "test-example". 

 


Generated at Mon Feb 12 00:37:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.