@AfterThrowing for unhandled exceptions?

[Praful Thakare]

Hi,

Tried @AfterThrowing in aspcet and what I understand is, its executed from the calling point as soon as there is exception but the exception still remains unhandled for example

         try
		{
			report.getReport();
		}catch(Exception e)
		{
			System.out.println("In Test class catch block...."+e);
		}

now if getReport() is adviced by afterThrowing and it throws some exception then afterThrowing is invoked and then control goes to catch,is there a way we can handle the exception in AfterThrowing advice?

code for getReport throwing exception

public int getReport()
	{

		System.out.println("This is getReport ");
		int x = 10/0;
	}

code for @AfterThrowing

@Pointcut("execution( * *.getReport())")
	public   void MethodAfterThrowing(){}
	
	@AfterThrowing(pointcut="MethodAfterThrowing()",throwing="ex")	
	public void MethodError(Exception ex)
	{
		System.out.println "After Exception >> " +ex.getMessage());
	}

I know this can be achived by @Around advice by putting proceed method in try catch, but can same be done without it?

-Praful

[Mark Spritzler]

No, In AfterThrowing, you cannot catch the exception, you can change the type of Exception or information in the Exception, but you still have to throw an exception through the Aspect.

Only in Around can you catch it and not re-throw one out.

Mark

[Praful Thakare]

ah okay, but would have been nicer if it was possible to do so, yes Around seems to be one stop shop, nothing else really required...

thanks

-Praful

[Mark Spritzler]

Praful Thakare wrote:ah okay, but would have been nicer if it was possible to do so, yes Around seems to be one stop shop, nothing else really required...

thanks

-Praful

Actually, it wouldn't be nicer. Only Around makes the developer responsible for exceptions, calling the target and returning the object returned from the target. All four other advices don't put those requirements on the developer and makes it nicer and easier.

Mark