[BLOSSOM-68] Incorrect validation method called on creation of nested new item Created: 26/Jan/12  Updated: 12/Apr/14  Resolved: 12/Apr/14

Status: Closed
Project: Blossom
Component/s: data-extension
Affects Version/s: Data Extension 1.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Erik Alphenaar Assignee: Tobias Mattsson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 4.4.5
magnolia-module-blossom 1.2.3
magnolia-module-blossom-extension-data 1.0.1
magnolia-module-data 1.6.4


Attachments: Java Source File CalendarFactory.java     Java Source File CalendarYearFactory.java     Zip Archive screenshots.zip    
Issue Links:
causality
caused by MGNLDATA-144 Validation does not work for subtype ... 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:

 Description   

I have a calendar structure in the Data Module for which I have all created @DataTypeDialogFactory classes with @DialogValidator or @TabValidator methods.

My test structure is as follows:
Calendar name > Calendar year > Calendar month > Calendar item

-The 'Calendar name' is the first item in this hierarchy. The validation works nicely. Checks if name is not empty (see attached CalendarFactory.java).
-When I create a new 'Calendar year' item below 'Calendar name', the correct TabFactory is called (see attached CalendarYear.java). When I hit save though, the validation method of 'Calendar year' is not called. Instead, the validation method of 'Calendar name' is called in CalendarFactory.java. See the 2 screenshots.

However, when I reopen an already created item, the validation works OK and the right method is called. So it seems to only fail when a new sub-node is created.



 Comments   
Comment by Tobias Mattsson [ 01/Feb/12 ]

Thanks for reporting this. I can reproduce the error. The problem is with the data module itself. Reported as MGNLDATA-144.

Comment by Tobias Mattsson [ 12/Apr/14 ]

Closing as duplicate since the problem needs to be fixed in the data module and is being tracked as MGNLDATA-144.

Generated at Sun Feb 11 23:29:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.