After thinking about it for a bit, I think the best thing to do is to go with a simple implementation of a new DeclaredMethodSignature since that has a minimal impact. This won't be integrated with the MethodSignature stuff. If it turns out in future that integration is required, we can modify the MethodSignature to support it and rework the DeclaredMethodSignature to be based on it. That way that calling code doesn't wouldn't need to change. Although we'd probably deprecate DeclaredMethodSignature if that was the case, (i.e. if MethodSignature gained an optional declaring class parameter) and remove it in JBossMDR 3.0? https://jira.jboss.org/jira/browse/JBMDR-35 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170392#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...