RE: XML Security C++: Incomplete cleanup in XSECC14n20010315 destructor

> I can see how it could occur if the canonicalisation gets interrupted in > the midst of outputting Attribute nodes. This fix would work nicely, > and I think it should be safe as the code that normally cleans up > ensures mp_attributes is NULL, so it won't get called unnecessarily. Ok, I checke

DO NOT REPLY [Bug 43197] New: - Canonicalizer.canonicalizeSubtree(Node) omits namespaces for Documents created with DocumentBuilder.newDocument()

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: XML Security C++: Incomplete cleanup in XSECC14n20010315 destructor

Berin Lautenbach wrote: Hmm. That's an interesting one. Have you seen a case where the mp_attributes list is not already clear when the destructor is called? Yes. That is why this fix has been appeared. But I can't remember those particular case for now, after almost three years :) Sorry for

Re: XML Security C++: Incomplete cleanup in XSECC14n20010315 destructor

Hmm. That's an interesting one. Have you seen a case where the mp_attributes list is not already clear when the destructor is called? I can see how it could occur if the canonicalisation gets interrupted in the midst of outputting Attribute nodes. This fix would work nicely, and I think it