You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jonas (JIRA)" <ji...@apache.org> on 2016/10/28 10:01:58 UTC

[jira] [Created] (WICKET-6264) Form: improve error message for disabled/invisible IFormSubmittingComponent

Jonas created WICKET-6264:
-----------------------------

             Summary: Form: improve error message for disabled/invisible IFormSubmittingComponent
                 Key: WICKET-6264
                 URL: https://issues.apache.org/jira/browse/WICKET-6264
             Project: Wicket
          Issue Type: Improvement
          Components: wicket
    Affects Versions: 7.5.0
            Reporter: Jonas
            Priority: Minor


org.apache.wicket.markup.html.form.Form.onFormSubmitted(IFormSubmitter) throws WicketRuntimeExceptions in case the IFormSubmittingComponent has is not/no longer enabled or visible.

A logged message looks like this:
{noformat}
2016-10-28 11:49:27,289 ERROR [org.apache.wicket.DefaultExceptionMapper] - Unexpected error occurred
org.apache.wicket.WicketRuntimeException: Submit Button ok (path=form:ok) is not enabled
	at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:772)
	at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:708)
...
{noformat}

This kind of problem is currently quite hard to fix, as neither the error message nor the stack trace contains any hint what page is affected.

I would like to propose to add e.g. the pages' class to both error messages, e.g. "Submit Button ok (path=form:ok) on page com.foo.bar.WebPage is not enabled" and "...visible"








--
This message was sent by Atlassian JIRA
(v6.3.4#6332)