Hi,
I am currently experimenting with JBoss-AOP and the annotation/metadata support. I
have noticed that for MethodInvocations the Class metadata is not part of path that is
used to resolved the metadata. See the code from MethodInvocation.java:
public Object getMetaData(Object group, Object attr) {
| Object val = super.getMetaData(group, attr);
| if (val != null) return val;
|
| if (getAdvisor() != null) {
| val = getAdvisor().getMethodMetaData().resolve(this, group, attr);
| if (val != null) return val;
| }
|
| if (getAdvisor() != null) {
| val = getAdvisor().getDefaultMetaData().resolve(this, group, attr);
| if (val != null) return val;
| }
|
| return null;
| }
I am wondering if there is a reason for this? If not, let me know and I will post a
patch to include it in the resolution path.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833968#3833968
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833968
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
