springbean is ok. although bends the rule rather then breaking it by not depending on any state of the super class.
if we did it the other way then the dependencies would be null during the constructor call, which is obviously something we want to avoid. -igor On Mon, Apr 28, 2008 at 6:22 AM, James Carman <[EMAIL PROTECTED]> wrote: > On Mon, Apr 28, 2008 at 8:31 AM, Maurice Marrink <[EMAIL PROTECTED]> wrote: > > > > > > Oooooh! Nasty. I thought you guys were somehow waiting until the > > > Component was fully instantiated for this notification to occur. If > > > > Nope. One of the places where this is used, is for security > > (intercepting if a component is authorized to be instantiated) in that > > case you want to abort as soon as possible. > > > > And the Spring listener actually makes @SpringBeans available during > the subclass' constructor. So, that would break also. Perhaps we > need an IAfterComponentInstantiationListener or something? Each > Component would append itself to a queue to be processed by all of the > after component instantiation listeners. > > > > --------------------------------------------------------------------- > 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]
