> > Even when using proxies this could get tricky if both try to implement > the same method. whichever implementation wins your app will not work > properly.
What do you mean by wins? Isn't this the same as how for instance Spring interception works. There you can add multiple interceptors to one bean. It is the developers responsibility that there are no conflicts. Lars On Fri, Apr 11, 2008 at 9:57 AM, Maurice Marrink <[EMAIL PROTECTED]> wrote: > On Fri, Apr 11, 2008 at 9:46 AM, Martijn Lindhout > <[EMAIL PROTECTED]> wrote: > > Can't we implement 'something' using an interceptor chain? Extensions > can > > register themselves in the Application#init() method. There might be a > chain > > for the webrequest cycle, for example. Each part in the chain may add > some > > behavior to the cycle then. > And how would conflicts be resolved then? for instance 2 extensions > that both require a custom websession? > Even when using proxies this could get tricky if both try to implement > the same method. whichever implementation wins your app will not work > properly. > I am afraid in those kinds of situations you still end up manually > merging the 2 implementations (if possible). > > Maurice > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
