On Fri, 18 Feb 2005 21:02:44 -0500, Ted Husted <[EMAIL PROTECTED]> wrote: > On Fri, 18 Feb 2005 09:04:32 -0800, Don Brown wrote: > > There is a middle ground which I have been playing with on and off > > frequently called "interceptors". In WebWork2, you can define > > action interceptors that intercept certain actions, defined at a > > per-action level. With Struts Action Invocation Framework (SAIF) > > at struts.sf.net/saif , we ported interceptors to pre-chain Struts, > > but it would be interesting to integrate that work with Struts as > > it is now. It would be nice to define code that would be executed > > only before certain groups of actions. > > Why not add a Command to the request processing chain that acts as an > interceptor. > > The Command looks for the group of Actions, does it's business when they come > along, and ignores the rest. > > -Ted. >
I may be mistaken on this, Don would be the expert of course on this, but I think that the idea of the interceptors on SAIF is to provide AOP support. Command/Chain would seem to work against the basic precepts of AOP, I think. I admint that I am not 100% confident of this statement. -- No one ever went blind looking at the bright side of life. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
