[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-users] AOP strategy

But... you could use an aspect to capture the basic Observer/Listener
behavior which then delegates to a Strategy, perhaps....

Ted Neward
Author, Instructor, Consultant
Java, .NET, Web services
http://www.neward.net/ted

> -----Original Message-----
> From: aspectj-users-admin@xxxxxxxxxxx [mailto:aspectj-users-
> admin@xxxxxxxxxxx] On Behalf Of Eric Bodden
> Sent: Friday, January 07, 2005 4:25 AM
> To: aspectj-users@xxxxxxxxxxx
> Subject: RE: [aspectj-users] AOP strategy
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> > Is this a good use case for AOP ?
> No, I would not think so. Since you wanna do *different* thing for
> every instance your concern is not really crosscutting. Actually I
> think it would be bad design anyway - also using standard OOP. If the
> listeners do different things for different shapes they should be
> related to them. The implementation you propose reminds me of
> "simulated OOP" in ANSI C passing parameters and using a lot of
> switch statements...
> 
> Eric
> 
> - --
> Eric Bodden
> Chair I2 for Programming Languages and Program Analysis
> RWTH Aachen University
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.3
> 
> iQA/AwUBQd5/rMwiFCm7RlWCEQJmbQCdG+nD8sjsYXxDkV2Bnhe61nvtZHsAoIkh
> vYvsGBtLkf+m7mtOqYkFW6b/
> =Y1f2
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users