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 29428] - Digester does not keep "root" variable in sync...
Date Tue, 08 Jun 2004 10:42:27 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=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 james@carmanconsulting.com  2004-06-08 10:42 -------
Ahhhh.  I see what you mean about the "first object created" stuff.  The 
Catalog example would fail.  However, the documentation isn't really clear on 
how the stack is supposed to work.  The idea that the first thing created by 
the rules will be returned isn't exactly obvious.  In my mind, I don't imagine 
anything to be on the stack at the end of parsing unless I push something on 
there to begin with, using most of the default rules.  So, when I use 
Digester, I usually push my "root" object onto the stack prior to parsing.  I 
didn't realize that the first object pushed onto the stack is what's supposed 
to be returned from parse().  That's not clear from the documentation.  Or, 
maybe that was just my misunderstanding.  I don't really like that little 
twist, though.  It doesn't seem as clean, if you ask me.  But, there's a LOT 
of code out there using it the way it is now, so we'd better not break it.  
And, you're right, my implementation WILL break a LOT of stuff.  Oops!

---------------------------------------------------------------------
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