Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-353

Description of volatile parameter for the Grid component is misleading, should be clear that application is responsible for the tracking the row

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15, 5.0.16
    • Fix Version/s: 5.1.0.4
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      I have written almost identical Java for examples of an editable Loop and an editable Grid where the Loop example requires volatile="true" but the Grid example does not. Why the difference?

      If I set volatile="true" in the Grid example then on submit I get an exception of the t:row field being null.

      You can see the working Loop and Grid at:
      http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/editableloop1
      http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/tables/editablegrid1

      I will attach the exception that occurs when Grid has volatile="true".

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: