Developers, At one time, and for quite some time, I've had a working web service client that would receive a signed SAML assertion in the form of an xsd:any, and be able to send that assertion back out, also in the form of an xsd:any. Since my cvs up, it seems that no longer works properly.
On the surface, it seems that some xmlns attributes have been lost. I see everything on the wire on the inbound, but on the outbound the assertion is significantly different. It almost looks like someone is optimizing xmlns attributes in MessageElement DOM. I assume that the sax recorder will have everything, but I haven't actually tried replaying into xerces DOM. First, let me make sure that I understand what should be happening. MessageElement can have many faces, and one such face is an implementation of DOM. Should I expect that the xsd:any element (which is a MessageElement) should have a complete DOM of what came in over the wire? In the past, that has been the case. Can anyone shed some light? ~S
