public class TFPExceptions{
public void translateException(Exception t) throws Throwable {
System.out.println(”TEST EXCEPTION HANDLED…..>>>>>>>>>3333333>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ” );
}
}

I am trying to wrap all my service exceptions to my customize exception but the problem is after the point cut also myExceptionTranslator it not getting called , following is the code

public class TFPExceptions{
public void translateException(Exception t) throws Throwable {
System.out.println(”TEST EXCEPTION HANDLED….. ” );
}
}

I am throwing a nullpointerException from my service
but after exception also it is not coming into translateException method,

Any comments much appreciated.

Raj

Regards
Sateesh Thumma

With my ‘after-throwing’ advice working I want to understand how ordering comes to play. The application I am working on has a few other aspects implementing around, before and now my after impl. I am not sure how ordering works implementing the Ordered interface and when I need to be concerned about ordering aspects.

Is ordering only applicable to the same advice type being invoked on the same pointcut? For example if the application has several after-throwing aspects on the same pointcut I can see ordering working as the one with the lowest order value is invoked first ect…

However, in this case the application has an around aspect providing Authorization on user role and method being invoked. If the user is not authorized to access the specified method an AuthorizationException is thrown. In this case I don’t want my after-throwing to convert this exception so I implemented the after-throwing advice to be aware of this AuthorizationException and simply rethrow. But, could I have used ordering to resolve this?

We also have aspect ‘arround’ advices providing method argument validation, transaction management ect. The application has one central AspectsOrderingConstants providing all the aspect ordering. But I am not sure how my after-throwing advice needs to respect the ordering if at all???

Any comments much appreciated.

Thanks,

Greg

glad I could help.

Much appreciated,

Greg

this is not very difficult: when using Spring 2.0 (I would definitely recommend this) you would have to the following inside a Spring XML file:

<aop :config>
<!– 1. Identify places where you think this is going to happen (in other words: where the exception should be ‘translated’ or ‘rethrown’). This is what you call a pointcut. –>
</aop><aop :aspect ref=”myExceptionTranslator”>
<aop :pointcut id=”serviceOperation” expression=”execution(* com.mycompany.service..*.*(..))”/>
<aop :after-throwing throwing=”exception” method=”translate”/>
</aop>

<bean id=”myExceptionTranslator” class=”com.mycompany.util.MyExceptionTranslator”/>

<bean id=”myService” class=”com.mycompany.service.MyService”/>

public class MyExceptionTranslator {

public void translate(MyFunnyRuntimeException e) {
throw new MyOtherFunnyRuntimeException(e);
}
}

Now remember: if you use Spring AOP, the advice will ONLY be applied to managed Spring beans (not to objects created by new()).

For more info on the pointcut expression language and AOP 2.0, look at the reference manual (http://static.springframework.org/spring/docs/2.5.x/reference/aop.html).

Let me know if you have any issues with it.

regards,
Alef