neilg 2003/01/16 09:14:03
Modified: java/src/org/apache/xerces/impl XMLEntityManager.java
Log:
if a SecurityManager has been enabled and the continue-after-fatal-error has
nonetheless been set to true, there seems no better way to continue than to reset the
entity expansion count once it has reached the limit and the fatalError has been
thrown. One could, in principle, use this to determine how much memory it cost for a
particular number of entity expansions.
Revision Changes Path
1.58 +5 -1 xml-xerces/java/src/org/apache/xerces/impl/XMLEntityManager.java
Index: XMLEntityManager.java
===================================================================
RCS file:
/home/cvs/xml-xerces/java/src/org/apache/xerces/impl/XMLEntityManager.java,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- XMLEntityManager.java 16 Jan 2003 17:10:10 -0000 1.57
+++ XMLEntityManager.java 16 Jan 2003 17:14:02 -0000 1.58
@@ -889,6 +889,10 @@
"EntityExpansionLimitExceeded",
new Object[]{new
Integer(fEntityExpansionLimit) },
XMLErrorReporter.SEVERITY_FATAL_ERROR
);
+ // is there anything better to do than reset the counter?
+ // at least one can envision debugging applications where this might
+ // be useful...
+ fEntityExpansionCount = 0;
}
// call handler
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
