Uploaded image for project: '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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.2.2
    • 5.2.3
    • tapestry-core
    • 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.

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: