[MGNLDATA-18] Add validation for specified additional node types in data type definition Created: 15/Feb/08  Updated: 15/Sep/15  Resolved: 31/Jul/09

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.4

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed 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   

When creating new (or editing existing) data type definition in data module it is possible to specify additional node types. However this information is not validated while saving thus allowing user to enter incorrect definition. The result of storing such incorrect node type reference is that after restart whole magnolia instance can't be started. The only way to fix such problem if it occurs is to either remove data repository or to connect to it externally and remove offending entry.



 Comments   
Comment by Philipp Bracher [ 18/Feb/08 ]

note: you can probably fix the custom_nodetype.xml file in repository directory

Comment by Jan Haderka [ 31/Jul/09 ]

The error in node type definition no longer prevents startup of data module. The error is now logged and module startup continues.
Added check directly while saving the dialog so invalid type is noticed at a save time and can be corrected immediately.

Done as of r26949.

Comment by Michael Mühlebach [ 15/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:10:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.