You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/11/05 20:10:44 UTC

[jira] Assigned: (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

     [ https://issues.apache.org/jira/browse/TAP5-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1332:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> In a multi-zone update, if the referenced Zone can not be found on the client, Tapestry stops updating Zones with no error
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1332
>                 URL: https://issues.apache.org/jira/browse/TAP5-1332
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.