All,
What if the commons-proxy library supported more "flavors" (a la AspectJ and
Spring) of AOP proxies instead of just one, the "around" advice using
MethodInterceptors?
public interface BeforeAdvice {
public void before(Method m, Object[] args, Object target);
}
public interface AfterReturningAdvice {
public void afterReturning(Object returnValue, Method m, Object[] args,
Object target);
}
public interface ThrowsAdvice {
public void afterThrowing(Method m, Object[] args, Object target,
Throwable t);
}
I'm also considering switching back to just directly using the
MethodInterceptor interface rather than coming up with our own interceptor
interface, since MethodInterceptor is somewhat standard. I wish the AOP
Alliance had these other "flavor" interfaces defined, too. What do you
folks think? Do you think this is too complex? I mean, you can accomplish
everything here using just MethodInterceptors. Should we add another layer
of complexity to it? I'm still kind of on the fence about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
