[CAUSEWAY-1541] When no explicit layout xml is available the order of the members is set to incorrect, ignoring other facets

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.13.0
• Fix Version/s: 1.13.2
• Component/s: Core
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 21/Nov/16 13:29
• Updated: 14/Dec/16 08:10
• Resolved: 24/Nov/16 10:44

Description

When no explicit layout xml is available the order of the members is set to incorrect, ignoring other facets (couldn't influence the order of the members in a table even with a non-Default TableOrderService)

The fix is in the order of member id in the GirdSystemService.