Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] How to intercept proceed() in around() advice

Alexander,

Agreed and I looked at the Stackoverflow post and thought about this one and the more I thought about it, to me the most "elegant" solution was to create an inheritance tree with your aspects that handled this case in a traditional OO maner.

One other thought, have you considered why you are always indenting/dedenting your logger and if that is necessary and/or a better design could be achieved in your logging implementation?

Ron DiFrango
________________________________________
From: aspectj-users-bounces@xxxxxxxxxxx [aspectj-users-bounces@xxxxxxxxxxx] on behalf of Alexander Kriegisch [Alexander@xxxxxxxxxxxxxx]
Sent: Wednesday, August 29, 2012 12:55 PM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] How to intercept proceed() in around() advice

Ron DiFrango, 29.08.2012 16:35:
> Or, is proceed sort of a generic delegator, can't a base Aspect
> class be created that wraps the common functionality into it and
> just accepts the message as the parameter and executes the code as
> required?

Thanks for this suggestion, Ron. As I said in my answer to Andy Clement:
There is always a way to work around limitations, and I found one. But
work-arounds are (at least for me) also always some kind of mental
"breakpoint" to stop and think about possible alternatives which might
not even exist yet, but be desireable.

Regards
--
Alexander Kriegisch
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users


Back to the top