Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML Transformation

From: "Anishek Agarwal" <anishek@-----.--->
To: xml-dev@-----.---.---
Date: 8/6/2008 4:54:00 AM
Hello,
I have a third party incoming XML at the transport layer which has a structure as below

<d:a xmlns:a="...." xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">

.....
.....
<dsig:Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> (the dsig namespace is applied to all child elements as well)

......
.....
</dsig:Signature>
</d:a>


When my parser is parsing the xml this is what i am getting 

<d:a xmlns:a="...." xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">


.....

.....

<Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> (the dsig namespace is removed from all the child elements)
......

.....

</Signature>

</d:a>


Then when i try to validate the signature it fails. The partner is saying that i have wrongly parsed the xml. They calculated the digest with the "dsig" prefix in their xml where as i am calcuating it after removing "dsig" namespace as there is a default namespace and thus the parser overrides the parent  namespace declaration. 


Which one is correct, should my parser have retained the "dsig" namespace even though a default namespace is defined or i am doing the right thing?

We are using apache axis 1.3 for parsing the xml which is comming over SOAP.


thanks in advance for the help

Regards,
Anishek


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent