[
https://issues.apache.org/jira/browse/WICKET-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832320#comment-16832320
]
Sven Meier commented on WICKET-6663:
------------------------------------
Hi Hans,
>The browser does not process the answer of a request before sending the next
>request.
this is not true for wicket-ajax, which queues all requests.
> Then Wicket processes Request R2, which targets now an invisible component.
For exactly this reason wicket-ajax aborts R2, if A's markup is no longer in
the DOM. And we changed it to handle placeholders in the same way.
> I just override canCallListener with \{ return true; }
That seems to circumvent Wicket's inbuilt security.
A quickstart would really help to support your arguments.
> 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
>
> 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)
