You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Brill Pappin (JIRA)" <ji...@apache.org> on 2007/11/09 04:03:50 UTC
[jira] Commented: (WICKET-1138) Better warning of design errors
during development
[ https://issues.apache.org/jira/browse/WICKET-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541216 ]
Brill Pappin commented on WICKET-1138:
--------------------------------------
First ideas:
- in development mode:
- an ERROR log entry is written.
or
- exception is actually thrown out
> 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.