Thanks Gurkan! I now also found the utility method who filters out the AROUND_INVOKE interceptors we need.
Did you look at the test code which shows the principal way to create subclasses which I committed? wdyt? LieGrue, strub --- Gurkan Erdogdu <[email protected]> schrieb am Mi, 7.4.2010: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Re: are @PostConstruct and @PreDestroy really interceptor functions? > An: [email protected] > Datum: Mittwoch, 7. April, 2010 21:19 Uhr > Those are not handled by > InterceptorHandler. These are defined in > AbstractInjectionTargetBean#postConstruct or preDestroy > > > > > ________________________________ > From: Mark Struberg <[email protected]> > To: [email protected] > Sent: Wed, April 7, 2010 7:56:37 PM > Subject: are @PostConstruct and @PreDestroy really > interceptor functions? > > Hi! > > Currently we handle @PostConstruct and @PreDestroy methods > via the InterceptorHandler. > > Is this really necessary? > > Those functions are directly called by the container in > very clear defined situations in the lifecycle. And they > always get called from _inside_ the container and not > triggered by any client code. > > So can we move those 2 out of the interceptor stack? > > wdyt? > > LieGrue, > strub > > __________________________________________________ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen > herausragenden Schutz gegen Massenmails. > http://mail.yahoo.com > > > > > ___________________________________________________________________ > Yahoo! Türkiye açıldı! http://yahoo.com.tr > İnternet üzerindeki en iyi içeriği Yahoo! Türkiye > sizlere sunuyor! __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
