RE: Xerces bug submission...

[ro...@us.ibm.com]

I'll put that on the list o' considerations for an upcoming release, but
its too late for the 3.1.0/1.1.0 release. We can always add one that you
can call at your own discretion, if you feel the need.

----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey@us.ibm.com



"Arnold, Curt" <Cu...@hyprotech.com> on 01/26/2000 08:19:06 AM

Please respond to xerces-dev@xml.apache.org

To:   "'xerces-dev@xml.apache.org'" <xe...@xml.apache.org>
cc:
Subject:  RE: Xerces bug submission...



Unfortunately, I think leaks will be a continuing source of complaints,
especially as the code base gets into to more applications.  Making an
uninitialize method available (which could be called from global object
destructors) that releases resources and restores each and every static
back
to null would seem to be an eventual requirement.

If the state was driven all the way back to load, then any calls after
uninitialize (or the destructor) would reload the resources and then leave
them dangling.  However, I would think this has to be a rare situation and
a
tolerable behavior.

Not the most pressing issue, but one that will eventually need to be
addressed.