This is a popular answer on such querstions ("use veil" and so on) :).
But it is not the case here, because we do not know whet to block here.
Beside this, in general I think it is not a good solution.

On Fri, Jul 4, 2014 at 12:30 PM, Ernesto Reinaldo Barreiro
<reier...@gmail.com> wrote:
> Block the UI?
>
>
> On Fri, Jul 4, 2014 at 12:13 PM, Daniel Stoch <daniel.st...@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I think such question occurs from time to time on this list, but I
>> have never found a good answer how to solve such problem in general.
>> The problem is similar to my last question:
>>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> but now there is a situation when link was removed from page (not
>> disabled).
>>
>> So page was rendered in a browser, on the server component tree was
>> changed, but user clicks a link in a browser before this changes will
>> be pushed to it. It leads to an exception:
>>
>> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> removed from page.
>> at
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> at
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> at
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> at
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>
>> How it should be properly handled in application? Unfortunately this
>> is not a dedicated exception to catch somewhere, but a common
>> WicketRuntimeException.
>>
>> --
>> Best regards,
>> Daniel
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to