Tapestry 5
  1. Tapestry 5
  2. TAP5-1332

In a multi-zone update, if the referenced Zone can not be found on the client, Tapestry stops updating Zones with no error

    Details

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

      Description

      In other words, if the server specified the id of an element that doesn't exist, an exception is thrown (aborting updates of all other zones) but the exception is not reported.

      Tapestry should use the console to display the error ("Zone 'xyz' could not be located.') and continue with the remaining zones.

        Activity

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.2.3 [ 12315474 ]
        Resolution Fixed [ 1 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development