[CAUSEWAY-1715] Service priority as defined by @DomainServiceLayout#menuOrder or @DomainService#menuOrder not honored.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.1
• Component/s: Core
• Assignee: Daniel Keir Haywood
• Reporter: Andi Huber
• Created: 12/Sep/17 13:44
• Updated: 25/Sep/17 04:55
• Resolved: 15/Sep/17 11:08

Description

It seems menu contributing service's will not always produce submenus ordered correctly:

I found a case, where menuOrder was not honored while 2 menu-services were both contributing to the same menu. The member sequence for each group was correct, but the order of the groups was wrong.

@DomainService(nature = NatureOfService.VIEW_MENU_ONLY)
@DomainServiceLayout(named="TODO", menuOrder="30.2")
public class A {

    @Action
    @MemberOrder(sequence = "1.1")
    public void getAProperty() {
        
    }

}

@DomainService(nature=NatureOfService.VIEW_MENU_ONLY)
@DomainServiceLayout(named="TODO", menuOrder="30.1")
public class B {

    @Action
    @MemberOrder(sequence = "1.1")
    public void getBProperty() {
        
    }

}

Menu group B should be positioned above group A, but it sometimes is not.