[
https://issues.apache.org/jira/browse/WICKET-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855597#comment-16855597
]
Hans Schäfer edited comment on WICKET-6663 at 6/4/19 11:36 AM:
---------------------------------------------------------------
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 :)
The showcase creates a situation, where the DOM-Tree is not in sync with
server-side state. This in consequence leads to a
ListenerInvocationNotAllowedException. My opinion is, that it is not possible
to avoid such situations. And in consequence: if you cant avoid such
situations, find a good way to handle such situations. I guess the initial idea
of "canCallListener" was to give the programmer a chance to handle the
ListenerInvocationNotAllowedException-situations. Perhaps it is a good idea to
make a Wicket-Application more configurable in handling the
"ListenerInvocationNotAllowedException" instead of trying to avoiding requests
via Javascript-Magic. I think about it and will try to find a proposal.
was (Author: hosea):
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 :)
The showcase creates a situation, where the DOM-Tree is not in sync with
server-side state. This in consequence leads to a
ListenerInvocationNotAllowedException. My opinion is, that it is not possible
to avoid such situations. And in consequence: if you cant avoid such
situations, find a good way to handle such situations. I guess the initial idea
of "canCallListener" was to give the programmer a chance to handle such
situations. Perhaps it is a good idea to make a Wicket-Application more
configurable in handling the "ListenerInvocationNotAllowedException" instead of
trying to avoiding requests via Javascript-Magic. I think about it and will try
to find a proposal.
> 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)
