[
https://issues.apache.org/jira/browse/WICKET-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541260
]
Gwyn Evans commented on WICKET-1138:
------------------------------------
If you did have a feedback panel, would there have been a message that would at
a minimum, point you in the right direction to find the problem?
If so, then maybe what we need to do is log any unprocessed warning or error
messages when in development mode.
> Better warning of design errors during development
> --------------------------------------------------
>
> Key: WICKET-1138
> URL: https://issues.apache.org/jira/browse/WICKET-1138
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-beta4
> Reporter: Brill Pappin
>
> As suggested in this list post:
> http://www.nabble.com/Form%3A-onSubmit-not-called-tf4763217.html#a13659761
> > Although it was my own fault hands down (silly me didn't write a test first)
> > I'm thinking that I could have saved hours with some sort of indication...
> > now that its happened once the lesson is pretty clear, but a lot of people
> > are going to stumble over stuff like that when they first get into Wicket.
> Yeah. If you can open up a JIRA issue for it, we can think/ discuss
> what we could do here.
> Eelco
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
