[MGNLXAA-20] Activation of non orderable nodes Created: 19/Aug/09  Updated: 30/Nov/10  Resolved: 15/Nov/10

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Sean McMains Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File patch.txt    
Issue Links:
Cloners
clones MAGNOLIA-2847 User Activation Issue Closed
relation
is related to MAGNOLIA-2713 different ordering of websites in Aut... Closed
is related to MAGNOLIA-2372 Nodes of the type ItemType.FOLDER can... 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)

 Description   

During activation, activated nodes are re-ordered to keep node order in sync with author instance. This is not possible for un-orderable nodes (e.g. child nodes of the node of the type nt:folder ). Since such children can't be ordered even in the author instance, preserving order for them is not important and should not cause activation to fail.
Setting fix to 1.2 since to Enable this in XA activation, the dependency to m-m-exchange-simple needs to be upped to 4.1.1 at least.


Generated at Mon Feb 12 11:06:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.