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 14:25 ------- thank you Simon for your attention. Sorry, but I know, that attributes from XML are generally Strings at first sight. And the conversion to match call parameters also works. But how can the digester know, that a String "converted" to an Object does not fit my needs? There's no problem filling the map, but on accessing the elements, I've the trouble, that all keys are Strings. Well, I could run over the map, copiing all entries to another map where I convert the keys, but I don't like that. I would like to have the keys the desired class before they are added to the map. I don't have trouble with a self written Rule. In this case, I'm filling a map. Works well with standard processing. Now I want the key of the map entries be of type Integer and I found no other way to solve this. When the attribute is fetched, it is a String. The method has to parameters of type Object, so no conversion will be neccesary. If I specify the Integer at CallMethodRule, no method is found - which looks quite natural for me, cause it's very difficult to do a type-conversion at method-lookup. So I first created a subclass of CallParamRule. Works fine for my needs. But then I thought, that others may have the same need/wishes as I. Therefor I added my changes. Well, if noone had/has the need to do this "conversion" before the method-call, no problem at all. Just kick my attachments and it's ok ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
