Hi Scott, thanks for all that information, it is much appreciated. I can see we still have to go a long way with DSig. Against this background, I have switched back to an alternative way of signing for now. I think I cannot get it to run with XMLSec in the time that I have left on this project - but the en/decryption, at least, works.
I think these things that I attempted are not too rare - having the XML go through different parsers and outputters. Transferring objects between VMs might also be something that people want to do, so I am not too sure if it is a good idea to check equality of namespaces by object reference. > > It's the identity transform - that should not do anything except store > > the DOMSource in a Result. > > Not if you're pretty printing with some kind of indent flag. That can't > possibly do what it says if it's really an identity transform.... Yeah, well, as I said, whether I set the indent flag or not does not affect the outcome. > > In essence, what I need is to transfer the XML between sender and > > receiver. What kind of serialisation would you recommend for the > > transfer? > > I definitely wouldn't use code that was likely to affect the DOM in any > way. I would simply write out the DOM node by node using a serializer that > was designed to do nothing else to it. Namespaces are another matter...it's You don't happen to have a code snippet around that does exactly that (Java)? Ralph -- For contact details, please see www.ralphholz.de.
signature.asc
Description: This is a digitally signed message part.
