Yes, that is what you want, no? On Thu, Jun 25, 2009 at 10:50 AM, Belvasis <[email protected]>wrote:
> But if i invoke the method on the DynProxyGetTarget() - object it bypasses > the interceptor, or do Ido something wrong? On the other hand > what you say means, you have alwys to know if an object is a proxy or not. > Is this wanted? > > Thanks and regards > > Am 25.06.2009 um 02:01 schrieb Ayende Rahien <[email protected]>: > > That is the expected behavior.Invoking a method using Invoke will mean > that you get back to the interceptor. > The workaround you specified is how this should work. > > On Thu, Jun 25, 2009 at 2:55 AM, Belvasis < <http://belvasis.de> > belvasis.de@ <http://googlemail.com>googlemail.com> wrote: > >> >> >> >> >> > >> >> > Hi, >> > I have the following problem: >> > I want to invoke a method on a proxy >> > using MethodInfo.Invoke(...). The method should be intercepted, if the >> > InterceptorSelector decided to do so. >> > The problem is, that the Interceptor.Intercept method is called in >> > an endless loop, if invocation.Proceed is called Inside the >> > interceptor. Anyone an idea why this happend? If i invoke the >> > corresponding MethodInfo of the DynProxyGetTarget() - object, it >> > works as expected. >> > >> > Thanks >> > Belvasis >> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
