> >Ack! I know there is a bug lurking there somewhere. I > can't wait to find > >it. :-) > > Hint: It's not a logic bug. It is related JavaBeans introspection. A > test case soliciting a configurator should reveal the problem.
Heh. I know what you are talking about on the MatchFilterBase class. When I did it, I was wondering if the Bean Property/OptionHandler would be able to deal with it. I have written code myself that when the basic bean introspection fails (because there is no matching getter/setter) it falls back to searching and calling the desired version of the method directly. I'll be sure to work it out. And the test case would not have caught this problem unless it was written to use a configuration file to set up the appender and filters. I'm thinking that using a configuration file should be part of the test case to get full coverage. -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
