[
http://jira.jboss.com/jira/browse/JBAOP-387?page=comments#action_12365160 ]
Kabir Khan commented on JBAOP-387:
----------------------------------
As long as it is a (subclass of) RuntimeException it doesn't really matter too much.
We've been a bit lazy until now, mostly throwing RuntimeExceptions, but as we spoke
about a while back having proper Exceptions improve the API. So, InvalidAdviceException
would be a good start.
Throw Exceptions when a valid advice is not found
-------------------------------------------------
Key: JBAOP-387
URL:
http://jira.jboss.com/jira/browse/JBAOP-387
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Flavia Rainone
Assigned To: Flavia Rainone
Fix For: 2.0.0.alpha5
We need to throw an exception warning the user that a valid advice method couldn't be
found for a specific joinpoint scenario. (currently, we are printing warnings in the
org.jboss.aop.advice.annotation.AdviceMethodFactory algorithm).
This task involves changes to org.jboss.aop.advice.PerVMAdvice and
org.jboss.aop.advice.annotation.AdviceMethodFactory classes.
We also need to update the documentation, telling when this runtime exception will be
thrown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira