You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2019/05/02 16:43:00 UTC

[jira] [Commented] (WICKET-6663) WICKET-6575 - please revert

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

Sven Meier commented on WICKET-6663:
------------------------------------

If you've used an invisible component *without* placeholder tag, your Ajax calls wouldn't have worked either, would they?

> WICKET-6575 - please revert
> ---------------------------
>
>                 Key: WICKET-6663
>                 URL: https://issues.apache.org/jira/browse/WICKET-6663
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 8.1.0
>            Reporter: Hans Schäfer
>            Priority: Major
>
> Hello!
> WICKET-6575 introduced a bug in my application.
> I explicitly make an Ajax-Call to an invisible component. In my case: this component displays search results as soon as they are available. The call is triggered by a script created by another (visible) component.
> The method "canCallListener" already models the behavior of components/behaviors regarding invocations. If you make Ajax-Calls to invisible components you can hook in here (the default-Implementation causes an exception if component is invisible) and make processing possible. This was a consistent server-side API until Wicket-6575.
> Please remove the changes of Wicket-6575. 
> Thanks
> Hans
>  
>  



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