I really think it depends what domain you are in.
>From my experience it can be exploited it in a number of areas outside
of frameworks, see my reply to Dick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java P
Hello everybody!
I have to say a very good discussion about AOP and its pro and cons!
After some experience I mostly agree with the sceptic view of Jess:
Leave AOP to the frameworkers.
When pondering about the different mindsets and attitudes towards AOP,
I spontaneously wrote this (please do n
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, se
What he said :-)
Dick
On Jul 24, 8:48 am, Jess Holle wrote:
> kinko wrote:
> > On Jul 23, 11:56 am, Jess Holle wrote:
>
> >> I don't actually have any flames for the Posse's AOP response, but Dick
> >> predicted flames, so I had to put that in the subject :-)
>
> > I really didnt agree with th
Hi Liam
Your examples are well taken, I guess I tend to think of using AOP as
the full on cross cutting defining hooks in XML files and so on, and I
have never used that. Indeed in Guice I tend not to use the AOP
features much either (unless you count the basic injection, which I
guess in some se
kinko wrote:
> On Jul 23, 11:56 am, Jess Holle wrote:
>
>> I don't actually have any flames for the Posse's AOP response, but Dick
>> predicted flames, so I had to put that in the subject :-)
>>
> I really didnt agree with the opinions voiced on the adoption, or
> rather non adoption of AO
On Jul 23, 11:56 am, Jess Holle wrote:
> I don't actually have any flames for the Posse's AOP response, but Dick
> predicted flames, so I had to put that in the subject :-)
I really didnt agree with the opinions voiced on the adoption, or
rather non adoption of AOP.
Have any of the panel ever us
In cases of /simple /"do this too" code any real possibility of
side-effects to the existing code, AOP makes sense.
Having done a lot of monitoring and logging code, I've found that in
many cases it involves much more (e.g. examining various existing local
variables or interweaving throughout e
hey there
On Thu, Jul 23, 2009 at 12:01 AM, Mikael Sundberg <
mikael.sundber...@gmail.com> wrote:
>
> Another time there was suddenly a requirement for logging all method calls
> and return values, once again... 3-4lines of aop.
>
> how could any of that have been done without AOP?
>
Isn't it th
Howdy, i use AOP some at work and cant realy see a way to do it any other
good way.
for example, management suddenly got the idea that everytime someone saves
anything in one application that should be monitored. So we can see who did
what. I looked some at annotations and such but that seemd like
One concrete use of AOP that I've seen that actually makes a lot of
sense is Spring's declarative transactions. They are implemented using
AOP so, for example all of your DAOs can be configured to be
transactional.
On Jul 23, 3:56 am, Jess Holle wrote:
> I don't actually have any flames for the
I still think AOP as a concept has been driven into containers,
libraries, and frameworks where it can be "managed" (and hidden).
Use of something like AspectJ for ordinary development rather than
bottled up and fully hidden by a container, library, or framework seems
/exceedingly /rare. Moreo
I just heard the comments of the posse and am quite disappointed. Not
because they seem to dislike it (as it's up to everybody to build
one's own opinion) but rather that the argumentatzion was build on a
good bunch of halfknowledge. Here are my points:
1) AOP is a concept. So how can one blame a
Having some experience in content management, I'd think that under the
covers this would not be done via aspects but rather via mix-in
interfaces and/or composition.
Alan Kent wrote:
> Jess Holle wrote:
>
>> So what is AOP good for? It's a powerful tool for building certain
>> types of libr
Jess Holle wrote:
> So what is AOP good for? It's a powerful tool for building certain
> types of library/framework capabilities. ...
Just relating a personal experience, I had read various bits on Aspect
Oriented Programming (or aspects in general) but they always seemed to
be vague descrip
15 matches
Mail list logo
