patch applied. always report a jira issue, that way things dont get forgotten, and as you can see submitting a patch helps too :)
-igor On Sun, Mar 30, 2008 at 9:36 PM, David Leangen <[EMAIL PROTECTED]> wrote: > > I didn't happen to see a reply to this thread, and the stack trace is > still driving me bananas, so I submitted a patch. :-) > > https://issues.apache.org/jira/browse/WICKET-1464 > > > Thanks, as always, Wicket committers. :-) > > > > > > > On Thu, 2008-03-13 at 12:45 +0900, David Leangen wrote: > > > > > > This used to work in 1.2.6, but now 1.3.1 complains that > > > > > > there is no setter for this class. > > > > > > > hmm, this should still work. mind filing a jira bug with > > > > > a quickstart? > > > > > > You're right, it does still work. The thing is that during the > algorithm > > > > when the properties of the bean are being tested the entire exception > > > > stack is being printed out. > > > > > > > > This is a bit confusing because it can lead the developer to think that > > > > an error occurred. > > > > > > > > > > > > I propose to log information instead of printing out the entire > > > > exception stack. If you agree to this, I don't mind submitting a patch. > > > > > What level is this reported to? > > > Its not error right? > > > > > > Current, DEBUG. > > > > Still, though, I think a logging message would be better than polluting > output with the entire stack trace... > > > > > > Cheers, > > Dave > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
