@Alexander
option c is my concern
very appreciate for your help , thanks again .
@Ron
thank you so much for your info
Just studying on that website
On Thu, Aug 30, 2012 at 10:46 PM, Ron DiFrango-2 [via AspectJ] <
ml-node+s2085585n4650508...@n4.nabble.com> wrote:
> If you are trying to implement
If you are trying to implement the logic of handling the exception then the
joinpoint "handler" is what you are after. Here is some sample code on the
aspectj site to look at:
http://www.eclipse.org/aspectj/sample-code.html#language-handlerContext
Ron DiFrango
Director / Architect | CapTech
Yes, I think I can help you if you tell me (in prose, not in code) what
you want to achieve: Do you want to
a) intercept and log the exceptions in your production code, then pass
them through (i.e. let them happen)?
b) intercept and log the exceptions in your production code, but *not*
thanks Alexander,
I'm waiting for any reply for long time :(
could you help me to make a simple demo of my example ?("caseName is a
method name of one testcase")
I will have a try that drop the *catch* block in my testcase
On Thu, Aug 30, 2012 at 5:34 PM, Alexander Kriegisch-2 [via AspectJ] <
ml-
The "after throwing" pointcut, as the name implies, matches joinpoints
*after* a method is *throwing* an exception. Your example method
"caseName", as far as I understand your code, does *not* throw any
exceptions, because it catches them, calls the logger/handler and then
exits gracefully.
--
Alex
