wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Grigorov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WICKET-3939) Double submit causes exception with panel replacement
Date Sat, 06 Aug 2011 21:43:27 GMT

     [ https://issues.apache.org/jira/browse/WICKET-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Grigorov updated WICKET-3939:
------------------------------------

    Priority: Minor  (was: Critical)

Wicket should not ignore requests.
This problem is easily solveable by disabling the submit button until it returns. Check the
mailing list archives for "Veil component", also there is a recipe in "Apache Wicket Cookbook".
 

> Double submit causes exception with panel replacement
> -----------------------------------------------------
>
>                 Key: WICKET-3939
>                 URL: https://issues.apache.org/jira/browse/WICKET-3939
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.4.17
>         Environment: java version "1.6.0_25"
> Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> Java HotSpot(TM) Client VM (build 20.0-b11, mixed mode, sharing)
>            Reporter: bernard
>            Priority: Minor
>         Attachments: quickstart.ZIP
>
>
> We are getting this critical error quite frequently - some users double click without
being aware of it.
> How to reproduce:
> In the attached quickstart, double click on the button fast, randomly.
> The crash seems to be caused by setVersioned(false); in the page constructor.
> org.apache.wicket.WicketRuntimeException: component panel:panel1Form not found on page
page.HomePage[id = 11], listener interface = [RequestListenerInterface name=IFormSubmitListener,
method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
> org.apache.wicket.protocol.http.request.InvalidUrlException: org.apache.wicket.WicketRuntimeException:
component panel:panel1Form not found on page page.HomePage[id = 11], listener interface =
[RequestListenerInterface name=IFormSubmitListener, method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
> 	at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:262)
> 	at org.apache.wicket.RequestCycle.step(RequestCycle.java:1310)
> 	at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436)
> 	at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
> 	at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:486)
> 	at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:319)
> We use setVersioned(false); to avoid unnessary browser history entries and unnecessary
session growth.
> I guess the exception can be explained easily from the technical perspective of the framework.
> However practically, from the application perspective, the exception is counter-productive.
> Simply speaking, is it possible that Wicket ignores requests for which a valid target
no longer exists?
> If Wicked ignored this undesired but possible state, then all would be fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message