public Object resolve(Invocation invocation, String group, String attr)
{
Method method = MethodInvocation.getMethod(invocation);
return getMethodMetaData(method.getName(), group, attr);
}
Am I missing something or is this code making the assumption that a
method's name provides sufficient discrimination amongst all possible
method metadata? If so, what is the architectural rationale behind that
usage?
I've noticed that in some other parts of jboss org.jboss.util.MethodHash is
used to construct a serializable and presumably unique key for a method
that does take into account both the methods name and list of parameter
types. Unfortunately for use w/jmx, the MethodHash also encodes the class
from which the method originates. Perhaps we can generalize MethodHash to
cover the case where the class is not known.
david jencks
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
