You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2002/09/27 23:20:44 UTC

DO NOT REPLY [Bug 13098] - Digester Performance

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=13098>.
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=13098

Digester Performance

rdonkin@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From rdonkin@apache.org  2002-09-27 21:20 -------
thanks for posting this to bugzilla, greg, and thanks for the figures.

(i had a feeling that your patch would turn out to be this.)

i've thought about this before and came to the conclusion that generic caching the right 
way to solve this problem. by this i mean that the caching should be done in the reflection 
layer rather than in the calling component. that way, every component using the 
reflection library can enjoy this advantage, not just digester.

i didn't realise that method caching made such a large difference (but i'm on java 1.3 and 
so reflection is s l o w) and i'll try to raise this issue as soon as lang is released. please stick 
around and join in the discussions. 

- robert

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>