ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35476] - XMLLogger causes OutOfMemoryError
Date Mon, 27 Jun 2005 12:11: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=35476>.
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=35476





------- Additional Comments From j_a_fernandez@yahoo.com  2005-06-27 14:11 -------
OK, is it every attribute that is unknown at the begining on the startXXX or 
just certain things like "elapsedTime" and "errorStack" (paraphasing).

Maybe we can just move the things that are really lookaheads to their correct 
place and make the logger generate SAX events. By using SAX, we gain the fact 
that we can pipe the events to a stylesheet XSLT, if you do not mind DOM, or 
STX if you want to continue with streamming (using joost). 

This would be way better. The only thing you need is a way to make sure all 
elements get close after a build fails so that we always get correct XML. I 
may have some XML SAX filter code that knkows how to do that. If needed.


-- 
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message