DO NOT REPLY [Bug 23100] - getElementById() returns element instance outside document tree

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23100] - getElementById() returns element instance outside document tree

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27803] - DOMBuilder doesn't load Schema for validation, fails instead

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27803] New: - DOMBuilder doesn't load Schema for validation, fails instead

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: memory corruption when deleting the SAXParser

I take it back. Given the nature of his problem, that was a dumb thing to say. But I stand by my suggestions (debugging, Purify-ing, building sample apps). > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, March 19, 2004 12:18 PM > To: [EMAIL PROTE

RE: memory corruption when deleting the SAXParser

> I don't recall whether creating a parser on the stack is supported, but you seem to have strong evidence that the answer is "no." I create parsers on the stack all the time without problems. Dave - To unsubscribe, e-mail:

DO NOT REPLY [Bug 25470] - attribut is already use by element (AttrAlreadyUseInSTag XMLBE50)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: memory corruption when deleting the SAXParser

I think that's a safe assumption. You're not spinning up any threads, and Xerces surely isn't. > -Original Message- > From: Nathan Smith [mailto:[EMAIL PROTECTED] > Sent: Friday, March 19, 2004 10:05 AM > To: '[EMAIL PROTECTED]' > Subject: RE: memory corruption when deleting the SAXParse

RE: memory corruption when deleting the SAXParser

Well, I would assume since the debugger returns from constructing the new object, it would not be still running in a thread when deleting the object (since the delete command is executed directly after the new object is created - just for debugging purposes). -Original Message- From: Pete

RE: memory corruption when deleting the SAXParser

Hi There I am wondering if there is still a thread in the Sax Parser running when you call the destructor for the parser. This would have unwanted results! Pete -Original Message- From: Nathan Smith [mailto:[EMAIL PROTECTED] Sent: 19 March 2004 13:41 To: '[EMAIL PROTECTED]' Su

RE: memory corruption when deleting the SAXParser

Well just to rule that out, I commented everything out after the Initialize statement except for the new SAXParser statement and the corresponding delete, and it still gave me the same error. -Original Message- From: Alberto Massari [mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004

RE: memory corruption when deleting the SAXParser

Title: Message I suppose it's possible that this problem would not occur with a newer version, but since we don't have any idea what the real issue is, it's hard to know. Even if it "went away," I'd be worried that the cause remained, even if it no longer manifested. In my experience, it's b