[
https://issues.apache.org/jira/browse/WICKET-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832332#comment-16832332
]
Sven Meier commented on WICKET-6663:
------------------------------------
Thanks for your detailled description:
Why are you insinsting on sending the request to the invisible
search-result-panel? You could equally well attach your behavior on any other
component (e.g. the parent panel) and let it unhide the search results.
You could even join these two behaviors into one, so it would listen for an
event on an input, and show *another* component as soon as it receives the
response from your search service.
BTW an IResource would be simpler than building a custom
IRequestMapper/IRequestHandler-Pair.
> 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)
