[jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-279) Check for InstanceAnnotation when doing hasMetaDataAtInstanceLevel in AOPConstructorJoinpoint

[Ales Justin (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-279?page=all ]

Ales Justin closed JBMICROCONT-279.
-----------------------------------

    Resolution: Done

This was added to AOPConstructorJoinpoint.
We check the whole hierarchy of ScopeLevels, startting from INSTANCE (including) level, excluding JOINPOINT level.

> Check for InstanceAnnotation when doing hasMetaDataAtInstanceLevel in AOPConstructorJoinpoint
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-279
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-279
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: AOP
>    Affects Versions:  JBossMC-2.0.0.Beta12
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>             Fix For: JBossMC.2.0.0.CR1
>
>
> When AOP asks whether there are instance annotations it does this to decide whether an instance proxy is required.
> In some cases, e.g. the @JMX annotation, the instance annotation does not require an instance proxy
> instead we are just reusing the point cut language to invoke "advices" during deployment.
> To better handle this case, we should be able to meta annotate an annotation as not requiring an instance proxy,
> e.g. something like:
> @org.jboss.metadata.spi.annotation.InstanceAnnotation(false)
> public @interface JMX
> {
> ...
> }
> then we can tell aop whether an instance proxy is required.

-- 
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