You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/05 15:36:00 UTC

[jira] [Commented] (WICKET-6528) Component part of Page check in AjaxRequestHandler breaks applications

    [ https://issues.apache.org/jira/browse/WICKET-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386219#comment-16386219 ] 

ASF GitHub Bot commented on WICKET-6528:
----------------------------------------

Github user dashorst commented on the issue:

    https://github.com/apache/wicket/pull/265
  
    Is merged with commit https://github.com/apache/wicket/commit/3be55cf5a24982cfca400225aabb6c4296859a7d


> Component part of Page check in AjaxRequestHandler breaks applications
> ----------------------------------------------------------------------
>
>                 Key: WICKET-6528
>                 URL: https://issues.apache.org/jira/browse/WICKET-6528
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 8.0.0-M8
>            Reporter: Martijn Dashorst
>            Priority: Blocker
>             Fix For: 8.0.0
>
>
> The check if a component is part of the page hierarchy where an Ajax response is generated for breaks client applications in a most unpleasant way. While this check is good™, it should only generate errors in development mode. In deployment mode it should ignore the component (like in versions prior to Wicket 8) and log it as an error (which is expected: the application is in error).
> See method `public void add(Component... components)` in AjaxRequestHandler for more details.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)