I understand. Thank you. On Mon, Mar 9, 2009 at 11:45 PM, hammett <[email protected]> wrote:
> > The proxy will be attached to the interface, not to the concrete > class.. so there will be no interception for the this pointer. > > > On Mon, Mar 9, 2009 at 6:55 PM, Germán Schuager <[email protected]> > wrote: > > Hi, I've a class like this: > > > > [Transactional] > > public class Comp : IComp > > { > > public void MethodA() > > { > > MethodB(); > > } > > > > [Transaction(TransactionMode.Requires)] > > public void MethodB() > > { > > doSomething(); > > } > > } > > > > public interface IComp > > { > > void MethodA(); > > void MethodB(); > > } > > > > When MethodB is called everything is fine, but when MethodA is called, > which > > in turn calls MethodB, the transaction is ignored. > > > > I've just spent some time trying to realize what was going on; since > MethodB > > has the Transaction attribute I was expecting it to start a transaction > no > > matter from where am I calling it. > > > > Is this a known issue? > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
