[TAPESTRY-1471] Controlling the order of properties within a BeanModel is too complex and needs an improved API

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.0.6
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 16/May/07 17:19
• Updated: 10/Sep/07 05:33
• Resolved: 10/Sep/07 05:33

Description

The use of a numeric order, to sort the properties within a bean model, is very unwieldy, especially when there's a desire to programmatically add new properties (often as new columns in a Grid).

It would be nice if the BeanModel had methods addFirst(), addLast(), addBefore() and addAfter() to allow precise positioning of added properties within the model, and perhaps a reorder() method to change the overall order in a single go.