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 02:03 ------- I'm not sure why you think this is necessary. CallParamRule does generally push *strings* onto the parameter stack. However CallMethodRule uses BeanUtils and ConvertUtils to convert these strings to appropriate types for the target method. The result is that the target method gets passed objects of the appropriate type without the user having to specify the parameter's class. >From the email thread that led to this bugzilla entry, I guess that you are accessing the parameter stack from a rule you have written which does not use BeanUtils and ConvertUtils like CallMethodRule does. I suggest that rather than apply the patch you include here, it would be better to modify your rule that peeks at the parameter stack to do the appropriate conversions instead. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
