[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Fwd: XML Transformation
- From: "Anishek Agarwal" <anishek@g...>
- To: xml-dev@l...
- Date: Wed, 6 Aug 2008 14:09:42 +0530
---------- Forwarded message ---------- From: Anishek Agarwal <anishek@g...>
Date: Wed, Aug 6, 2008 at 2:09 PM Subject: Re: XML Transformation To: Michael Kay < mike@s...> Hello, Thanks Michael for the reply. i tried to debug the axis code and found that the socket stream was taken by the SAXParser to parse so i thought it was the parser that converted the stream to xml format. As for namespaces i understand the fact that the definition of the namespace for the given elements is still the same, its just that the prefix has changed. As per my understanding both the xml mentioned in the first mail above, after canocalization should give same xml so that their digest value is same but looks like our case its different, and the thirdparty software guys are claiming that since our parser (or XSLT transformer) has removed the namespace prefix the digest is diferent and hence the digital signature is failing.
AnishekOn Wed, Aug 6, 2008 at 1:51 PM, Michael Kay <mike@s...> wrote:
Firstly, when you say "parser", I suspect you mean
"XSLT processor". (It's a common mistake, but in cases like this it's important
to be precise).
Secondly, you say that the namespace is being removed from
these elements, but I don't think that's true: they are still in the same
namespace, only the prefix has changed. Correct me if I have
misunderstood.
For better or worse, the digital signature mechanisms
follow XML Canonicalization by deciding that namespace prefixes are significant:
see
http://www.w3.org/TR/xml-c14n#NoNSPrefixRewriting
for discussion.
XSLT 2.0 gives you complete control over the prefixes that
are used in your result tree. XSLT 1.0 gives the implementation a lot of
discretion in theory, but in practice it is usually possible to persuade the
processor to use the prefixes that you want.
Michael Kay
http://www.saxonica.com/
From: Anishek Agarwal
[mailto:anishek@g...] Sent: 06 August 2008 05:54Subject: XML
Transformation
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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|