Hi all, Can someone else verify this? It seems that upgrading to 2.1.5 breaks, at the least, new XMLDocuments. TIA Phil phil.harris@zope.co.uk
Phil Harris wrote:
Hi all,
Can someone else verify this?
Yes. Actually, there is a buglet in XMLDocument that was made effective by a fix to a bug in Acquisition. Prior to 2.1.5, there were cases where acquisition-wrapped objects sometimes didn't have their full acquisition context. This was fixed in 2.1.5. Unfortunately, some applications may depend on the old incomplete wrapping. :( In 2.1.5, when you add an XML document, you get a WrongDocumentException. This can be fixed by changing: if document and ownerDocument and document != ownerDocument: to: if (document and ownerDocument and getattr(document, 'aq_base', document) is not getattr(ownerDocument, 'aq_base', ownerDocument) ): in the appendChild method in class Node in file Node.py. There may be other problems, however, I'm not very familiar with XMLDocument and wouldn't be a good person to find them. Perhaps you could apply this patch and see if you can find anything else wrong. If you do, please provide me and Amos with some sample data and instructions for reproducing the problem. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
participants (2)
-
Jim Fulton -
Phil Harris