[
http://jira.jboss.com/jira/browse/JBAOP-560?page=comments#action_12412950 ]
Flavia Rainone commented on JBAOP-560:
--------------------------------------
Thre is one more problem of differentiating "null created aspects" from not
created aspects. The methods
ScopedRepositoryClassLoaderDomain.getPerVmAspectWitNoParentDelegation (line 64),
GeneratedClassAdvisor.ClassAdvisorStrategy.getPerClassAspect (line 1648) and
ClassProxyContainer.getPerClassAspect (line 201) use the nullity of an aspect to indicate
that they need to search for the aspect elsewhere. There is nothing to indicate whether
the aspect is null because it has been created that way and, hence, the aspect does not
need to be searched, or whether the aspect is not there and need to be searched
elsewhere.
Any suggestions?
When an AspectFactory returns null no interceptor should be added to
the chain
------------------------------------------------------------------------------
Key: JBAOP-560
URL:
http://jira.jboss.com/jira/browse/JBAOP-560
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR8
Reporter: Carlo de Wolf
Assigned To: Flavia Rainone
Fix For: 2.0.0.GA
--
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