Description

A trait defined as a multivalue field which contains a composite composed by two textFields is stored at JCR in different ways on Magnolia 5.7 and Magnolia 6.2.

Steps to reproduce

1. On Magnolia 5.7, import the trait in the attachments named config.modules.mgnl-common-module.traits.TESTING5UI.yaml
2. Create a page, add a Variant and on the Choose audience option, select the new trait
3. Create a couple of composite fields and fulfilled the both textfields (text and link)
4. Save the trait and move to JCR tools
5. On the variant, open the voter and check that the structure is as in the 5.7-storage.png image
6. Now, start a > 6.2.18 Magnolia project
7. Import the config.modules.mgnl-common-module.traits.TESTING6UI.yaml
8. Double check that the migration to the new UI has been made following the official guide
   # Create a page, add a Variant and on the Choose audience option, select the new trait
9. Create a couple of composite fields and fulfilled the both textfields (text and link)
10. Save the trait and move to JCR tools
11. On the variant, open the voter and check that the structure is as in the 6.2-storage.png image

Expected results

By following the official Magnolia 6 UI ports of 5 UI field transformer classes, the data is stored same way on Magnolia 5 and on Magnolia 6

Actual results

The data is missing a contentNode which prevents the node2Bean transformer to work as supposed

Workaround

N/A

Development notes

Its very important to achieve the very same storage behavior as far as the contentNode which contains the voters (named "fields", "items" whatever) must match the property List<Bean> nodeName so the node2Bean maps into a List all the voters.