Xerces (3.11) naturally generates EndOfEntityException when reading XML entities. This exception is thrown in ReaderMgr::popReader(), at least one for each entity. That's fine, except that the debug handling of those exceptions by MSDEV takes way too much time (twice the time, in fact). When huge files are processed, execution becomes way too slow. So, I'm wondering if there's a way of preventing those exceptions to be thrown by overriding something somewhere in xerces.
The exception in question is thrown under the following conditions: (prevEntity && (fThrowEOE || prevReaderThrowAtEnd)) Are any of these variable somehow "configurable" to force the no-exception path and still get the job done? I've looked at creating my own EntityResolver, but that doesn't seem to do the trick, as the "wrapping" default reader created by xerces makes it so that the prevReaderThrowAtEnd is set to true... (I'd even settle for some quick and dirty MSDEV trick that turns off the DEBUG handling of those) Thx, d. -- View this message in context: http://old.nabble.com/EndOfEntityException---Performance-in-DEBUG-tp29956646p29956646.html Sent from the Xerces - C - Users mailing list archive at Nabble.com.
