[
https://issues.apache.org/jira/browse/WICKET-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541500
]
Eelco Hillenius commented on WICKET-1138:
-----------------------------------------
Validation errors of user input is nothing exceptional though. So in that
sense, I don't think we should log errors, not even in development mode. I
could agree with warnings and then only when in development mode. I'm not sure
whether we should pass the stack trace by default. I think we should log enough
information so that you don't need it.
> 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.
