commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33873] New: - Named stacks are not popped at end of processing
Date Mon, 07 Mar 2005 08:06:47 GMT
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=33873>.
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=33873

           Summary: Named stacks are not popped at end of processing
           Product: Commons
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P4
         Component: Digester
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: brian@interscales.com


The method org.apache.commons.digester.Digester.endDocument() pops the main
stack in a loop, but does not perform the same operation on stacksByName. This
is inconsistent, and may result in an ever-growing stack if a Digester instance
is cached and reused (notwithstanding documentation that Digester instances
should not be reused anyway).
An alternative to clearing stacksByName in endDocument() would be to do so in
clear().

It also would be more consistent (and useful) to have a method
public Object peek(String stackName, int n);

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message