[MGNLCT-116] JackrabbitInitializer cannot handle .cnd files Created: 22/Feb/19  Updated: 04/Jun/19  Resolved: 06/Mar/19

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1

Type: Bug Priority: Major
Reporter: Christoph Meier Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 56m
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLRES-325 Resources app cannot display or edit ... Closed
Template:
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:
Sprint: Foundation 5, Foundation 6
Story Points: 5

 Description   

In a content-ype definition, when using the nodeTypeDefinition property pointing to a .cnd file:

nodeTypeDefinition: /content-type-examples-ee/jcr-node-type-files/travellers-node-types.cnd

JackrabbitInitializer fails to register what is defined in the .cnd file.

Apparently JackrabbitInitializer expects in any case an XML-based node-type definition, which is not true anymore. Since MAGNOLIA-7430, the file to define nodetypes and namespaces can be XML or CND.

=> Complete stack-trace



 Comments   
Comment by Christoph Meier [ 26/Feb/19 ]

For the guy who tackles this one:
I have a light module - content-type-examples-ee - which is using the .cnd files.
Master is using the XML file, branch feature/MAGNOLIA-7440 is using the .cnd file.

(However ... it requires an EE-Pro webapp

=>

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