Hi Ben, The terms "encrypted file" and "unencrypted file" probably have a particular meaning to you but doubt it's clear to anyone on the list what those XML documents actually contain. The SAX parser wouldn't normally require that much memory and would imagine that the devil is somewhere in the details that you haven't shared with us yet.
Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Benjamin Sanno <ben.sa...@online.de> wrote on 09/15/2010 05:52:53 AM: > My problem is explained in detail in : > > http://forums.sun.com/thread.jspa?messageID=11047827� > > Please have a closer look at the PDF documents that are attached. > > I found, that the Xerces parser doesn't allow the Garbage Colletor to > deallocate last XML Elements (as JAVOLUTION does). In general, I > coundn't measure the typical Streaming-Parser behavior: relatively > constant and low memory usage over time. > > is this a bug? > > thanks > > Ben Sanno > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org
