[Springframework-developer] Fw: Memento Pattern

[Rod J. <rod...@in...>]

Forwarded on behalf of Bob, who's having problems posting to the list...

I think this is actually not dissimilar to what I proposed, with the
IntroductionAdvice corresponding to my Advice.

I think the present MethodPointcut can cover both Class and method case.

I think we should introduce a new "Pointcut" superinterface for
MethodPointcut, even if it's a tag interface at present, and have Advice
return Pointcut, not MethodPointcut. Although I don't think Spring should
support field interception, and don't much like it in principle, we
shouldn't rule options out in our API.

I'm  inclining towards implementing the Advice interface I proposed. I'm not
planning to implement the Aspect interface for now, supporting multiple
Advices in one object, although that can be added later.

Regards,
Rod

----- Original Message ----- 
From: "Bob Lee" <cra...@cr...>
To: "Rod Johnson" <rod...@in...>
Sent: Friday, November 07, 2003 7:41 PM
Subject: Re: Memento Pattern


> Rod,
>
> I keep getting an error when I try to send to the list (detailed below).
>
> Here's my suggestion for the interfaces:
>
> interface ClassCut {
>   boolean appliesTo(Class clazz, ...);
> }
>
> interface MethodCut {
>   boolean appliesTo(Method method, ...);
> }
>
> interface InterceptionAdvice {
>   ClassCut getClassCut();
>   MethodCut getMethodCut();
>   [Method]Interceptor getInterceptor();
> }
>
> interface IntroductionAdvice {
>   ClassCut getClassCut();
>   Class[] getInterfaces();
>   [Method]Interceptor getInterceptor();
> }
>
> This gives you the separation and orthogonality you need and leaves the
> door open for performance optimization.
>
> You could refactor out an Advice super interface, but I don't see the
> benefit.
>
> Thanks,
> Bob
>
> P.S. I was able to send okay the other day. Here's the mail error:
>
> Nov  7 14:26:52 server qmail: 1068236812.632418 starting delivery 34:
> msg 4337993 to remote spr...@li...
> Nov  7 14:26:52 server qmail: 1068236812.632437 status: local 0/10
> remote 1/20
> Nov  7 14:27:08 server qmail: 1068236828.373999 delivery 34: deferral:
>
66.35.250.206_does_not_like_recipient./Remote_host_said:_451-Could_not_compl
ete_sender_verify_callout/451-Could_not_complete_sender_verify_callout_for_<
cra...@cr...>./451-The_mail_server(s)_for_the_domain_may_be_tempora
rily_unreachable,_or/451-they_may_be_permanently_unreachable_from_this_serve
r._In_the_latter_case,/451-you_need_to_change_the_address_or_create_an_MX_re
cord_for_its_domain/451-if_it_is_supposed_to_be_generally_accessible_from_th
e_Internet./451_Talk_to_your_mail_administrator_for_details./Giving_up_on_66
.35.250.206./
>
> I wonder what changed...
>
>
>
>