[
https://issues.apache.org/jira/browse/WICKET-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542720
]
Gwyn Evans commented on WICKET-1138:
------------------------------------
Yes, it's logged as a feedback message, but I don't think that just the debug
log's good enough when there's no feedback panel, as globally setting 'debug'
provides too much of a flood of info.
How feasible is it to be able to (in DEV mode) detect any unprocessed feedback
messages and log any error/warning ones at those logging levels? Not
stack-traces, but just the msg itself & the fact it's unprocessed or would that
generate too much info in 'normal' development?
> 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
> Assignee: Eelco Hillenius
> Fix For: 1.3.0-rc2
>
>
> 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.
