DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29428>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29428 Digester does not keep "root" variable in sync... ------- Additional Comments From [EMAIL PROTECTED] 2004-06-08 22:05 ------- i'm happy that clear does what it should do: it cleans the stacks. i'd probably favour a separate reset() method rather than breaking the contact for clear(). it is possible (in some cases) for a single digester instance to parse multiple input documents in sequence. it's just that the typical use case is to create a new digester instance in each case and so multiple sequential usage has never really been supported. in terms of http://www.mail-archive.com/[EMAIL PROTECTED]/msg06390.html, i'm a little sceptical about the performance of pooled digester instances verses creating new instances each time (at least in modern JVMs). depending on the level of concurrency and the number of digester rules, the cost of the synchronization required by the pool may outweigh the construction cost. i would be interested to see some actual timings. anyway, i suspect that it'd be possible to add a reset method that would work for most rulesets (those that clean up after themselves in finish). i'd prefer for any implementation to wait until after the 1.6.0 release branch is taken. Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
