[
https://issues.apache.org/jira/browse/WICKET-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541228
]
Brill Pappin commented on WICKET-1138:
--------------------------------------
You could do that, and it would catch a bunch at once if you had more than one
"unconsumed" message... but I'm thinking simpler as I may not *want* to consume
all the messages.
>From my point of view, all I really needed was something to say "I tried to
>save this value back to your model but got an error that said X".
You'd get that message immediatly when a converter failed (in my case, string
to date).
I guess I see this as a bug in my code rather than something I "should" have
done in good style, and I don't want Wicket trying to decide what good style
is, or try and guess what I meant to do.
However, I think indicating that there were errors that where not displayed in
any way would also be helpful in getting people to add a feedback panel, so
maybe we have two entry points into this potential problem.
> 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.
