[MAGNOLIA-7283] Type mismatch in Map2BeanTransformer shows no problem Created: 19/Mar/18  Updated: 10/Apr/18  Resolved: 10/Apr/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.6.3
Fix Version/s: 5.6.5

Type: Task Priority: Neutral
Reporter: Martin Drápela Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 3h
Time Spent: 2d 5h
Original Estimate: 3d

Issue Links:
Relates
relates to MGNLREST-180 Handle NPE of nodeTypes Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: YAML backwards compatibility
Sprint: Saigon 139, Saigon 140, Saigon 141, Saigon 142
Story Points: 3

 Description   

Given the endpoint configuration below, although nodeTypes is recognized in Definitions app, it doesn't match with the property in ConfiguredJcrDeliveryEndpointDefinitionJcrDeliveryEndpoint eventually receives a null nodeTypes on requests.

class: info.magnolia.rest.delivery.jcr.v2.JcrDeliveryEndpointDefinition
workspace: website
bypassWorkspaceAcls: true
nodeTypes: mgnl:page

 Problems tab is expected to show something like

Configured nodeTypes does not match with the corresponding property in ConfiguredJcrDeliveryEndpointDefinition

 



 Comments   
Comment by Dai Ha [ 10/Apr/18 ]

Verified with bundle magnolia-enterprise-pro-demo-bundle-5.6.6-20180410.033353-2-tomcat-bundle.zip. Given above config then a minor warning show up in definition app.

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