[MAGNOLIA-2773] Return simple property value if multivalued property wasn't properly created on import Created: 09/Jun/09  Updated: 23/Jan/13  Resolved: 09/Jun/09

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

Type: Improvement Priority: Major
Reporter: Teresa Miyar Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLCAT-10 Category RSS missing in public instan... Closed
relation
is related to MAGNOLIA-3968 Improve saveHandler for multiSelect c... 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)
Date of First Response:

 Description   

When exporting nt:unstructured node that has array property with exactly one value (eg String[1]), then exported XML structure is ambiguous. After import (which also implies activation is impacted too) it creates simple single-value (non-array) property.

see https://issues.apache.org/jira/browse/JCR-1464



 Comments   
Comment by Fabrizio Giustina [ 09/Jun/09 ]

new feature in 4.1-rc5? Where is the "no commit unless a real blocker" gone?

Comment by Teresa Miyar [ 09/Jun/09 ]

my mistake when creating the issue, it is indeed a blocker in Magnolia EE

Comment by Magnolia International [ 09/Jun/09 ]

Multivalue support was introduced in 4.0. It is used amongst others by a module we're releasing with EE 4.1, and this fix is necessary to make it work properly.

Generated at Mon Feb 12 03:39:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.