Hi Dick I suppose you have had different experiences from my work. I have found AOP a very powerfull paradigm in integrating with alot of proprietary API's especially todo with entitlements and security. To beable to simply say @Entitled, rather than the rest of the boiler plate, user lookups, service calls, is a real blessing.
Agreed closure ideas do also help in these concerns, Spring demonstrates this kind of, in the best way Java supports currently, with the template pattern. And dont get me wrong I think Java needs some kind off closures, the forkjoin examples prove this much alone. But still I feel the annotation delivery is far more expresive and concise in these examples. I think also there could be interesting ideas in concurrency coming from the use of AOP and annotations. I feel AOP and annotations have the same initial problem to users. >From the offset it is pretty difficult to see the point, but once you get to grips with them the application domain becomes very broad. Another example which I have found very usefull is for transient failures, to beable to mark a method as @Retryable, and not need to think about the try, catch , backoff etc , is great. I agree with the point above, yes frameworks will probably be the most broad usecase, but I also think they have alot of applications to the general developer. Depends in what domain you are working I feel Cheers for the interesting podcast Liam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
