> > > > 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]
