[MGNLREST-186] ReadNode gives wrong node order at depth>1 Created: 28/Mar/18  Updated: 02/May/18  Resolved: 03/Apr/18

Status: Closed
Project: Magnolia REST Framework
Component/s: delivery
Affects Version/s: 2.0.2
Fix Version/s: 2.1.1

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: 7h
Time Spent: 1d 1h
Original Estimate: 2d

Issue Links:
causality
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:
Sprint: Saigon 141
Story Points: 3

 Description   

At the 2nd level of response from the v2 delivery endpoint the nodes have the wrong order in the array.

To reproduce - use this enpdoint config: (/delivery/travel1.yaml)

class: info.magnolia.rest.delivery.jcr.v2.JcrDeliveryEndpointDefinition
workspace: website
rootPath: /
includeSystemProperties: false
depth: 2
nodeTypes:
 - mgnl:page
childNodeTypes:
 - mgnl:page

Hit this url: http://localhost:8080/magnoliaAuthor/.rest/delivery/travel1/travel

 

The response for the "about" page includes this:

....

  "about": {
    "@name": "about",

    ....

    "@nodes": [
      "what-we-believe",
      "careers",
      "company"
    ]

....

Whereas the actual order is:

  • company
  • what-we-believe
  • careers

 



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

QA with below bundles and artifacts:

magnolia-enterprise-pro-demo-bundle-5.6.4-20180403.174027-58-tomcat-bundle.zip
magnolia-rest-content-delivery-2.1.1-20180403.093400-8.jar
magnolia-rest-integration-2.1.1-20180403.093359-8.jar
magnolia-rest-services-2.1.1-20180403.093359-8.jar

With provided configuration in ticket description, observe that readNode maintains consistent node order. Closing ticket.

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