|
From: Rod J. <rod...@in...> - 2003-07-29 07:41:10
|
It failed for me with 1.4.1_01 on Win 2K. Anyway, should be no more problems now. ----- Original Message ----- From: "jürgen höller [werk3AT]" <jue...@we...> To: "Rod Johnson" <rod...@in...>; <spr...@li...> Cc: <spr...@li...> Sent: Tuesday, July 29, 2003 8:11 AM Subject: RE: [Springframework-user] Re: [Springframework-developer] BeansErrorHandler: missing method > Funnily enough, it actually *does* work on JDK 1.4.1_01, 1.4.1_02, 1.4.1_03, 1.3.1_04, and 1.3.1_07, on Windows 2000 and XP. Anyway, using an own logger instance to avoid any hassle is definitely the best option. > > Juergen > > > -----Original Message----- > From: Rod Johnson [mailto:rod...@in...] > Sent: Tuesday, July 29, 2003 8:53 AM > To: jürgen höller [werk3AT]; > spr...@li... > Cc: spr...@li... > Subject: Re: [Springframework-user] Re: [Springframework-developer] > BeansErrorHandler: missing method > > > > For curiosity's sake, do you know what *exactly* can cause the inner class > logger access to fail? Is this a VM respectively bytecode issue? > > Not really. It's strange that it compiles but doesn't work. I guess it's a > VM issue. I think that relying on a protected inherited outer class variable > is actually illegal in Java. I just don't understand why it compiled. > > I'm posting to the thread. > > > |