Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1471

Controlling the order of properties within a BeanModel is too complex and needs an improved API

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.6
    • Component/s: tapestry-core
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              hlship Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: