Hi folks! This should be working. At least that was exactly the reason why we have a 'CreationalContext' in our interfaces ;) It's only purpose is to make cyclic bean references work.
LieGrue, strub --- Eric Covener <[email protected]> schrieb am Fr, 20.11.2009: > Von: Eric Covener <[email protected]> > Betreff: Re: Inheritance of class local interception and lifecyle invocation? > An: [email protected] > Datum: Freitag, 20. November 2009, 17:32 > On Fri, Nov 20, 2009 at 11:15 AM, > Sven Linstaedt > <[email protected]> > wrote: > > Hi, > > > > has someone tested the correct order of class local > interception and > > lifecycle invocation in the case of inherited beans, > like it is specified in > > 4.2.? > > > > Like: > > > > class A { > > @PostConstruct > > void initA() {} > > } > > > > class B extends A { > > @PostConstruct > > void initB() {} > > } > > Haven't here, but would be interested in your findings. > > I believe even basic interceptor ordering via beans.xml is > currently > non-deterministic so cross your fingers! > > -- > Eric Covener > [email protected] > __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
