Take a look here is this similar to what you are talking about: http://cvs.apache.org/viewcvs.cgi/incubator/directory/ldap/trunk/sandbox1/jn di-provider/src/java/org/apache/ldap/server/jndi/?root=Apache-SVN
These are the relevant classes - ignore the rest of the JNDI stuff in that directory. AfterFailurePipeline DirServerContext FailFastPipeline Interceptor InterceptorException InterceptorPipeline Invocation InvocationStateEnum Alex > -----Original Message----- > From: Hamilton Verissimo de Oliveira (Engenharia - SPO) > [mailto:[EMAIL PROTECTED] > Sent: Monday, February 16, 2004 11:46 AM > To: Avalon Developers List > Subject: RES: FW: [Proposal] Augmenting Fortress extensions support > > -----Mensagem original----- > De: Alex Karasulu [mailto:[EMAIL PROTECTED] > > > On Monday 16 February 2004 19:48, hammett wrote: > > > Why not one proxy and a calling chain? The use could add his steps to > > the > > > chain and be happy about it. > > > You guys taking about a chain of services being injected with > interceptors > > here? Sorry I'm coming in late to this one. > > Don't think so :-) > > I'm talking about using a single Proxy (InvocationHandler) and this > constructs a chain of other parties interested in the method execution. > Got > it? > > Just like: > > AvalonProxy -> SecurityLayerPhase -> TransactionalLayerPhase -> > UserLayerPhase -> Execution > > and backwards... > > > > -- > hammett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
