You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Hans Schäfer (JIRA)" <ji...@apache.org> on 2019/06/04 11:25:00 UTC
[jira] [Commented] (WICKET-6663) Don't prevent requests on
component placeholders (revert WICKET-6575)
[ https://issues.apache.org/jira/browse/WICKET-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855597#comment-16855597 ]
Hans Schäfer commented on WICKET-6663:
--------------------------------------
Hi [~svenmeier],
unfortunately it took some time, until I could provide a showcase. I added it as .tgz-File. I hope, it will make things more clear :)
> Don't prevent requests on component placeholders (revert WICKET-6575)
> ---------------------------------------------------------------------
>
> 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
> Attachments: wicket-case.tgz
>
>
> 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)