DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23001>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23001 extended CallParamRule ------- Additional Comments From [EMAIL PROTECTED] 2003-09-10 22:23 ------- Hmm .. so the problem is that you *know* that the param you are passing to the target method is an Integer, but the target method has prototype: put(String key, Object obj) therefore CallMethodRule takes the simplest route of passing the String object extracted from the XML, because it matches Object. Did you try using the variant of CallMethodRule that takes an array of parameter types? Class[] paramTypes = { String.class, Integer.class }; digester.addCallMethod(method, nparams, paramTypes); >From looking at the source of CallMethodRule, it does use ConvertUtils to convert the string param objects into exactly the type specified before invoking the target method. [Note: haven't tested this myself] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
